Production-Grade Container Scheduling and Management
Go to file
2020-12-15 22:59:57 +00:00
.github Update triage/support label references to kind/support 2020-10-01 20:09:37 -04:00
api Update generated swagger API 2020-12-14 11:17:07 +08:00
build [go1.15] Use go-runner:buster-v2.2.2 image (built on go1.15.5) 2020-11-23 21:23:25 -05:00
CHANGELOG Merge pull request #96948 from 249043822/bugfix-changelog112 2020-12-14 17:45:48 -08:00
cluster Make log-dump's deprecation note up-to-date 2020-12-15 09:58:09 +01:00
cmd update cloud-controller-manager samples to read --cloud-config flag 2020-12-15 10:56:22 -08:00
docs Add sigs for root folders 2020-08-13 10:24:06 -04:00
hack Fix OpenAPI spec generator script 2020-12-14 10:10:33 +08:00
LICENSES vendor: cadvisor v0.38.4 2020-11-13 19:52:57 +00:00
logo Merge pull request #93975 from avr1254/master 2020-09-03 06:16:09 -07:00
pkg Merge pull request #97221 from 249043822/br-scheduler-metrics 2020-12-14 17:45:56 -08:00
plugin Merge pull request #97020 from mikedanese/errfix 2020-12-08 21:06:42 -08:00
staging update cloud-controller-manager samples to read --cloud-config flag 2020-12-15 10:56:22 -08:00
test Merge pull request #96834 from chendave/fix_race 2020-12-15 07:13:49 -08:00
third_party test images: Removes -p yes flag from qemu-user-static script call 2020-11-04 23:01:24 +00:00
translations add initial translation for pt_BR 2020-12-11 17:06:42 +01:00
vendor vendor: update cAdvisor to v0.38.6 2020-12-09 15:11:26 -08:00
.bazelrc
.bazelversion
.generated_files Purge almost all memories of godep 2020-05-07 21:49:00 -07:00
.gitattributes
.gitignore Add openapi generation for the kube-aggregator 2020-06-05 11:10:08 +08:00
.kazelcfg.json
BUILD.bazel
CHANGELOG.md
code-of-conduct.md
CONTRIBUTING.md Remove stale analytics links from docs 2020-11-18 07:04:48 -06:00
go.mod vendor: update cAdvisor to v0.38.6 2020-12-09 15:11:26 -08:00
go.sum vendor: update cAdvisor to v0.38.6 2020-12-09 15:11:26 -08:00
LICENSE
Makefile
Makefile.generated_files
OWNERS Move brendandburns to to emeritus status. 2020-08-27 10:20:56 -04:00
OWNERS_ALIASES Requesting reviewers status for SergeyKanzhelev 2020-12-15 22:59:57 +00:00
README.md Use K8s in the README 2020-11-12 11:23:23 -08:00
SECURITY_CONTACTS
SUPPORT.md
WORKSPACE

Kubernetes (K8s)

GoDoc 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.