Production-Grade Container Scheduling and Management
Go to file
Abu Kashem 3182b69e97
apiserver: add a new mode for graceful termination
add a new mode for graceful termination with the new server run option
'shutdown-send-retry-after'
- shutdown-send-retry-after=true: we initiate shutdown of the
  HTTP Server when all in-flight request(s) have been drained. during
  this window all incoming requests are rejected with status code
  429 and the following response headers:
    - 'Retry-After: N' - client should retry after N seconds
    - 'Connection: close' - tear down the TCP connection
- shutdown-send-retry-after=false: we initiate shutdown of the
  HTTP Server as soon as shutdown-delay-duration has elapsed. This
  is in keeping with the current behavior.
2021-08-10 15:53:37 -04:00
.github
api Regenerate openapi 2021-08-09 17:04:31 -04:00
build Merge pull request #104245 from m-Bilal/fix-buildx-dependency-documentation 2021-08-10 05:55:18 -07:00
CHANGELOG Merge pull request #104146 from saschagrunert/dependencies-duplicate 2021-08-05 08:18:57 -07:00
cluster Update debian-base image to buster-v1.9.0 2021-08-07 09:44:59 +08:00
cmd Merge pull request #104248 from liggitt/drop-beta 2021-08-10 11:52:40 -07:00
docs
hack pin-dependencies.sh: support switching repos 2021-08-09 16:54:30 +02:00
LICENSES vendor: bump runc to 1.0.1 2021-07-16 12:36:26 -07:00
logo
pkg Merge pull request #104248 from liggitt/drop-beta 2021-08-10 11:52:40 -07:00
plugin Merge pull request #103704 from robscott/endpoints-write-remove 2021-07-19 20:57:31 -07:00
staging apiserver: add a new mode for graceful termination 2021-08-10 15:53:37 -04:00
test Merge pull request #104248 from liggitt/drop-beta 2021-08-10 11:52:40 -07:00
third_party remove unused third_party/intemp 2021-03-08 21:17:37 -08:00
vendor Refactor goroutine counting 2021-08-10 10:37:53 -04:00
.generated_files
.gitattributes
.gitignore
CHANGELOG.md
code-of-conduct.md
CONTRIBUTING.md
go.mod Merge pull request #102913 from pacoxu/upgrade-promotheus-common 2021-08-09 08:03:31 -07:00
go.sum Merge pull request #102913 from pacoxu/upgrade-promotheus-common 2021-08-09 08:03:31 -07:00
LICENSE
Makefile
Makefile.generated_files
OWNERS
OWNERS_ALIASES Merge pull request #103620 from thockin/kal-approver 2021-07-22 19:29:16 -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.