Production-Grade Container Scheduling and Management
Go to file
Patrick Ohly 018b44daa6 component-base: avoid accumulating default labels
The intention in
ecb3813726
was to use the component-base/OWNERS labels only as fallback when the OWNERS
files in the sub-directories don't set labels. This should never have been
necessary because all of those sub-directories have reasonable labels
configured.

But in practice, the labels were also added to PRs that only touched files in
sub-directory because OWNERS files are inherited, which created noise in
various sigs that shouldn't have been tagged for those PRs.
2021-10-07 16:54:58 +02:00
.github Merge pull request #104058 from MadhavJivrajani/kind-design-rm-pr-template 2021-10-04 03:13:07 -07:00
api move IPv6DualStack feature to stable. (#104691) 2021-09-24 16:30:22 -07:00
build Merge pull request #105158 from justaugustus/its-a-bullseye 2021-09-26 23:14:23 -07:00
CHANGELOG CHANGELOG: Update directory for v1.23.0-alpha.3 release 2021-09-28 12:58:38 +00:00
cluster Merge pull request #105500 from ibabou/update_owners_cluster_gce 2021-10-06 09:58:41 -07:00
cmd Merge pull request #104631 from perithompson/kp-userspace-deprecation 2021-10-06 15:32:32 -07:00
docs
hack update hack/verify-structured-logging.sh 2021-10-05 17:50:05 +05:30
LICENSES klog 2.20.0, logr v1.1.0, zapr v1.1.0 2021-09-09 14:43:43 +02:00
logo
pkg Merge pull request #105455 from shivanshu1333/patch-1 2021-10-06 18:45:46 -07:00
plugin PodSecurity: add namespace update verify benchmark 2021-10-04 12:26:30 -04:00
staging component-base: avoid accumulating default labels 2021-10-07 16:54:58 +02:00
test Merge pull request #105337 from Huang-Wei/pr-105303 2021-10-06 19:53:56 -07:00
third_party Copy golang license to staging copies 2021-08-10 17:37:28 -04:00
vendor Merge pull request #104920 from tkashem/response-writer-cleanup 2021-10-05 00:53:09 -07:00
.generated_files
.gitattributes
.gitignore
CHANGELOG.md
code-of-conduct.md
CONTRIBUTING.md
go.mod run hack/{pind-dependency.sh, update-vendor.sh} 2021-09-30 19:15:43 +05:30
go.sum run hack/{pind-dependency.sh, update-vendor.sh} 2021-09-30 19:15:43 +05:30
LICENSE
Makefile
Makefile.generated_files
OWNERS
OWNERS_ALIASES Merge pull request #104186 from pacoxu/patch-2 2021-10-05 15:24:57 -07:00
README.md
SECURITY_CONTACTS
SUPPORT.md

Kubernetes (K8s)

GoPkg Widget CII Best Practices


Kubernetes, also known as K8s, is an open source system for managing containerized applications across multiple hosts. It provides basic mechanisms for deployment, maintenance, and scaling of applications.

Kubernetes builds upon a decade and a half of experience at Google running production workloads at scale using a system called Borg, combined with best-of-breed ideas and practices from the community.

Kubernetes is hosted by the Cloud Native Computing Foundation (CNCF). If your company wants to help shape the evolution of technologies that are container-packaged, dynamically scheduled, and microservices-oriented, consider joining the CNCF. For details about who's involved and how Kubernetes plays a role, read the CNCF announcement.


To start using K8s

See our documentation on kubernetes.io.

Try our interactive tutorial.

Take a free course on Scalable Microservices with Kubernetes.

To use Kubernetes code as a library in other applications, see the list of published components. Use of the k8s.io/kubernetes module or k8s.io/kubernetes/... packages as libraries is not supported.

To start developing K8s

The community repository hosts all information about building Kubernetes from source, how to contribute code and documentation, who to contact about what, etc.

If you want to build Kubernetes right away there are two options:

You have a working Go environment.
mkdir -p $GOPATH/src/k8s.io
cd $GOPATH/src/k8s.io
git clone https://github.com/kubernetes/kubernetes
cd kubernetes
make
You have a working Docker environment.
git clone https://github.com/kubernetes/kubernetes
cd kubernetes
make quick-release

For the full story, head over to the developer's documentation.

Support

If you need support, start with the troubleshooting guide, and work your way through the process that we've outlined.

That said, if you have questions, reach out to us one way or another.