mirror of https://github.com/kubernetes/kops.git
Update IMDSv2 docs
This commit is contained in:
parent
a2b811f68c
commit
f490b27e39
|
@ -47,9 +47,9 @@ spec:
|
|||
|
||||
## instanceMetadata
|
||||
|
||||
By default IMDSv2 are enabled as of kOps 1.22 on new clusters using Kubernetes 1.22. The default hop limit is 3 on control plane nodes, and 1 on other roles.
|
||||
By default, IMDSv2 is enabled for newly created clusters. The default hop limit is 1 for all node roles, except for control plane nodes with Kubernetes version lower than 1.26 or IRSA disabled, for which the default hop limit is 3. As of Kubernetes 1.27, these defaults are applied to existing clusters also.
|
||||
|
||||
On other versions, you can enable IMDSv2 like this:
|
||||
To enable IMDSv2 add the following configuration to the instance group:
|
||||
|
||||
```YAML
|
||||
spec:
|
||||
|
@ -58,6 +58,14 @@ spec:
|
|||
httpTokens: required
|
||||
```
|
||||
|
||||
To disable IMDSv2 add the following configuration to the instance group:
|
||||
|
||||
```YAML
|
||||
spec:
|
||||
instanceMetadata:
|
||||
httpTokens: optional
|
||||
```
|
||||
|
||||
## externalLoadBalancers
|
||||
|
||||
Instance groups can be linked to up to 10 load balancers. When attached, any instance launched will
|
||||
|
|
|
@ -8,6 +8,8 @@ This is a document to gather the release notes prior to the release.
|
|||
|
||||
## AWS
|
||||
|
||||
* As of Kubernetes version 1.27, all nodes will default to running with the instance metadata service enabled, with max hop limit of 1. Control plane nodes with IRSA disabled will default to running with a max hop limit of 3.
|
||||
|
||||
## GCP
|
||||
|
||||
# Breaking changes
|
||||
|
|
Loading…
Reference in New Issue