Production-Grade Container Scheduling and Management
Go to file
Claudiu Belu 94ac896269 test images: Simplifies the agnhost binary version
Currently, whenever agnhost/VERSION is bumped, the version in
agnhost/agnhost.go has to be bumped as well. This is also verified
on presubmit (build/dependencies.yaml).

This means that whenever we need to bump the agnhost image version,
someone has to approve the build/dependencies.yaml, which is not as
easy.

This commit removes the need for this check by automatically setting
the Version inside agnhost.go at build time, simplifying the process.
2021-08-11 09:12:03 +00:00
.github
api Merge pull request #102981 from SataQiu/add-ephemeral-config-v1alpha1 2021-08-05 20:55:12 -07:00
build test images: Simplifies the agnhost binary version 2021-08-11 09:12:03 +00: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 #102981 from SataQiu/add-ephemeral-config-v1alpha1 2021-08-05 20:55:12 -07:00
docs
hack Merge pull request #104164 from dims/allow-override-of-cgo-enabled 2021-08-05 16:37:26 -07:00
LICENSES vendor: bump runc to 1.0.1 2021-07-16 12:36:26 -07:00
logo
pkg device manager: do not clean admitted pods from the state 2021-08-08 16:46:06 +03:00
plugin Merge pull request #103704 from robscott/endpoints-write-remove 2021-07-19 20:57:31 -07:00
staging Merge pull request #104212 from MikeSpreitzer/event-clock-cleanup2 2021-08-09 00:29:31 -07:00
test test images: Simplifies the agnhost binary version 2021-08-11 09:12:03 +00:00
third_party remove unused third_party/intemp 2021-03-08 21:17:37 -08:00
vendor Some cleanup of the package for event clocks 2021-08-07 00:07:31 -04:00
.generated_files
.gitattributes
.gitignore
CHANGELOG.md
code-of-conduct.md
CONTRIBUTING.md
go.mod Merge pull request #104134 from ihgann/topic/ganni/optimize-kubeadm-etcd-member-add-2 2021-08-05 16:37:03 -07:00
go.sum Update golang.org/x/time/rate (#104014) 2021-07-29 16:13:38 -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.