kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #17431 from rifelpet/node-lifetime-doc 

Add documentation on max node lifetime
This commit is contained in:
Kubernetes Prow Robot 2025-06-11 22:50:56 -07:00 committed by GitHub
parent b1081c48ab 33a8df60c2
commit b806afca12
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/getting_started/production.md
View File

@ -20,6 +20,14 @@ By default, kOps will create IPv4 clusters using public topology, where all node
Read through the [topology page](../topology.md) to understand the options you have running nodes in internal IP addresses and using a [bastion](../bastion.md) for SSH access.
## Node Lifetime
Kops components issue certificates valid for approximately 15 months including for kubelet.
Kops doesn't support automatic rotation of kubelet certificates.
Therefore nodes may be lost once their certificate expires.
It is recommended to limit the lifetime of k8s nodes to 1 year, either by running `kops rolling-update cluster` periodically or a controller that drains and replaces nodes.
## Cluster spec
The `kops` command allows you to configure some aspects of your cluster, but for almost any production cluster, you will want to change settings that are not accessible through the CLI. The cluster spec can be exported as a yaml file and checked into version control.