Skip to content

Commit 983e32c

Browse files
authored
Merge pull request #854 from catlike/improve-eks-ug-docs-al2023
update latest/ug/nodes/al2023.adoc to include documentation and examp…
2 parents c95e327 + 8b8ee0b commit 983e32c

File tree

1 file changed

+21
-1
lines changed

1 file changed

+21
-1
lines changed

latest/ug/nodes/al2023.adoc

Lines changed: 21 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,27 @@ spec:
3131
cidr: 10.100.0.0/16
3232
----
3333
+
34-
In AL2, the metadata from these parameters was discovered from the Amazon EKS `DescribeCluster` API call. With AL2023, this behavior has changed since the additional API call risks throttling during large node scale ups. This change doesn't affect you if you're using managed node groups without a launch template or if you're using [.noloc]`Karpenter`. For more information on `certificateAuthority` and service `cidr`, see ` link:eks/latest/APIReference/API_DescribeCluster.html[DescribeCluster,type="documentation"]` in the _Amazon EKS API Reference_.
34+
In AL2, the metadata from these parameters was discovered from the Amazon EKS `DescribeCluster` API call. With AL2023, this behavior has changed since the additional API call risks throttling during large node scale ups. This change doesn't affect you if you're using managed node groups without a launch template or if you're using [.noloc]`Karpenter`. For more information on `certificateAuthority` and service `cidr`, see link:eks/latest/APIReference/API_DescribeCluster.html[`DescribeCluster`,type="documentation"] in the _Amazon EKS API Reference_.
35+
* For AL2023, `nodeadm` also changes the format to apply parameters to the `kubelet` for each node using https://awslabs.github.io/amazon-eks-ami/nodeadm/doc/api/#nodeconfigspec[`NodeConfigSpec`]. In AL2, this was done with the `--kubelet-extra-args` parameter. This is commonly used to add labels and taints to nodes. An example below shows applying `maxPods` and `--node-labels` to the node.
36+
+
37+
[source,yaml,subs="verbatim,attributes"]
38+
----
39+
---
40+
apiVersion: node.eks.aws/v1alpha1
41+
kind: NodeConfig
42+
spec:
43+
cluster:
44+
name: test-cluster
45+
apiServerEndpoint: https://example.com
46+
certificateAuthority: Y2VydGlmaWNhdGVBdXRob3JpdHk=
47+
cidr: 10.100.0.0/16
48+
kubelet:
49+
config:
50+
maxPods: 110
51+
flags:
52+
- --node-labels=karpenter.sh/capacity-type=on-demand,karpenter.sh/nodepool=test
53+
----
54+
+
3555
* [.noloc]`Docker` isn't supported in AL2023 for all supported Amazon EKS versions. Support for [.noloc]`Docker` has ended and been removed with Amazon EKS version `1.24` or greater in AL2. For more information on deprecation, see <<dockershim-deprecation>>.
3656
* Amazon VPC CNI version `1.16.2` or greater is required for AL2023.
3757
* AL2023 requires `IMDSv2` by default. `IMDSv2` has several benefits that help improve security posture. It uses a session-oriented authentication method that requires the creation of a secret token in a simple HTTP PUT request to start the session. A session's token can be valid for anywhere between 1 second and 6 hours. For more information on how to transition from `IMDSv1` to `IMDSv2`, see link:AWSEC2/latest/UserGuide/instance-metadata-transition-to-version-2.html[Transition to using Instance Metadata Service Version 2,type="documentation"] and link:security/get-the-full-benefits-of-imdsv2-and-disable-imdsv1-across-your-aws-infrastructure[Get the full benefits of IMDSv2 and disable IMDSv1 across your {aws} infrastructure,type="blog"]. If you would like to use `IMDSv1`, you can still do so by manually overriding the settings using instance metadata option launch properties.

0 commit comments

Comments
 (0)