Production-Grade Container Scheduling and Management
Go to file
Andrew Gunnerson b9ab65d689
certificate_manager: Check that template differs from current cert before rotation
With the current behavior, when kubelet starts, a `templateChanged`
event is always fired off because it only checks if `getLastRequest`
matches `getTemplate`. The last request only exists in memory and thus
is initially `nil` and can't ever match the current template during
startup.

This causes kubelet to request the signing of a new CSR every time it's
restarted. This commit changes the behavior so that `templateChanged` is
only fired off if the currently template doesn't match both the current
certificate and the last template.

Fixes #69471

Signed-off-by: Andrew Gunnerson <andrew.gunnerson@us.ibm.com>
2018-10-24 17:14:58 -04:00
.github
api Merge pull request #66605 from islinwb/default_RevisionHistoryLimit 2018-10-08 10:41:46 -07:00
build Manual changes to package visibility 2018-10-11 22:01:06 +02:00
cluster Merge pull request #68288 from loburm/truncating_backend 2018-10-11 18:26:34 -07:00
cmd NodeLifecycleController treats node lease renewal as a heartbeat signal 2018-10-11 16:07:15 -07:00
docs Merge pull request #66605 from islinwb/default_RevisionHistoryLimit 2018-10-08 10:41:46 -07:00
Godeps Update etcd client to 3.3.9 2018-10-08 13:34:34 -07:00
hack Merge pull request #69633 from soltysh/move_templates 2018-10-12 10:07:07 -07:00
logo
pkg Merge pull request #69633 from soltysh/move_templates 2018-10-12 10:07:07 -07:00
plugin Merge pull request #67934 from tanshanshan/typo828 2018-10-11 18:26:24 -07:00
staging certificate_manager: Check that template differs from current cert before rotation 2018-10-24 17:14:58 -04:00
test Merge pull request #69241 from wangzhen127/heartbeat 2018-10-12 03:32:15 -07:00
third_party
translations
vendor Update etcd client to 3.3.9 2018-10-08 13:34:34 -07:00
.bazelrc
.generated_files
.gitattributes
.gitignore
.kazelcfg.json
BUILD.bazel
CHANGELOG-1.2.md
CHANGELOG-1.3.md
CHANGELOG-1.4.md
CHANGELOG-1.5.md
CHANGELOG-1.6.md
CHANGELOG-1.7.md
CHANGELOG-1.8.md
CHANGELOG-1.9.md Update CHANGELOG-1.9.md for v1.9.11. 2018-10-01 18:56:09 +00:00
CHANGELOG-1.10.md
CHANGELOG-1.11.md
CHANGELOG-1.12.md Update CHANGELOG-1.12.md for v1.12.1. 2018-10-05 17:58:29 +00:00
CHANGELOG.md
code-of-conduct.md
CONTRIBUTING.md
LICENSE
Makefile
Makefile.generated_files
OWNERS
OWNERS_ALIASES
README.md
SECURITY_CONTACTS
SUPPORT.md
vendordiff.patch Update etcd client to 3.3.9 2018-10-08 13:34:34 -07:00
WORKSPACE

Kubernetes

GoDoc Widget CII Best Practices


Kubernetes is an open source system for managing containerized applications across multiple hosts; providing 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 you are a company that 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 Kubernetes

See our documentation on kubernetes.io.

Try our interactive tutorial.

Take a free course on Scalable Microservices with Kubernetes.

To start developing Kubernetes

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.
$ go get -d k8s.io/kubernetes
$ cd $GOPATH/src/k8s.io/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.

Analytics