kubernetes/kubectl

Issue tracker and mirror of kubectl code

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 5 minutes ago
Added to GitGenius on September 20th, 2026
Created on March 30th, 2017
Open Issues & Pull Requests: 100 (+0)
GitHub issues: Enabled
Number of forks: 1,018
Total Stargazers: 3,345 (+0)
Total Subscribers: 64 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 82
New in 7 days: 1
Closed in 7 days: 3
Avg open age: 1,275 days
Stale 30+ days: 68
Stale 90+ days: 42

Recent activity

Opened in 7 days: 1
Closed in 7 days: 2
Comments in 7 days: 1
Events in 7 days: 1

Top labels

  • needs-triage (207)
  • kind/feature (160)
  • kind/bug (139)
  • triage/accepted (101)
  • sig/cli (100)
  • priority/backlog (58)
  • lifecycle/rotten (55)
  • area/kubectl (24)

Detailed Description

kubectl is a command-line interface tool for managing Kubernetes clusters.

The tool addresses the need for a standardized way to interact with Kubernetes clusters through a command-line interface. It provides packages intended for use by client programs that need to communicate with Kubernetes APIs and manage cluster resources. The approach separates reusable packages from the CLI client itself, allowing these packages to be vendored into other projects without requiring a dependency on the full Kubernetes repository.

Developers should adopt this tool if they are building applications that need to interact with Kubernetes clusters or if they are creating CLI tools that extend kubectl functionality. The project suits teams working within the Kubernetes ecosystem who need reliable, well-tested packages for cluster management. This repository is specifically a staging area for kubectl code; contributions should be made to the main Kubernetes repository rather than here, and this repository serves primarily as an issue tracker and mirror for importing packages.

The project maintains strict contribution standards requiring full unit-test coverage, Go tool compliance to ensure packages remain vendorable elsewhere, and useful code commentary for both internal developers and external users. Packages are designed to implement sensible, small interfaces with limited dependency sets, following Golang code review best practices.