diff --git a/latest/ug/clusters/create-cluster-auto.adoc b/latest/ug/clusters/create-cluster-auto.adoc index e15788a7..8e01e746 100644 --- a/latest/ug/clusters/create-cluster-auto.adoc +++ b/latest/ug/clusters/create-cluster-auto.adoc @@ -279,7 +279,7 @@ aws iam attach-role-policy \ + ** Replace [.replaceable]`region-code` with the {aws} Region that you want to create your cluster in. ** Replace [.replaceable]`my-cluster` with a name for your cluster. The name can contain only alphanumeric characters (case-sensitive), hyphens, and underscores. It must start with an alphanumeric character and can't be longer than 100 characters. The name must be unique within the {aws} Region and {aws} account that you're creating the cluster in. -** Replace [.replaceable]`1.30` with any eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported version,type="documentation"]. +** Replace [.replaceable]`1.30` with any link:eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported version,type="documentation"]. ** Replace [.replaceable]`111122223333` with your account ID ** If you have created differently named IAM Roles for the Cluster and Node roles, replace the ARNs. ** Replace the values for `subnetIds` with your own. You can also add additional IDs. You must specify at least two subnet IDs. diff --git a/latest/ug/clusters/create-cluster.adoc b/latest/ug/clusters/create-cluster.adoc index 12b641c3..ca86dadc 100644 --- a/latest/ug/clusters/create-cluster.adoc +++ b/latest/ug/clusters/create-cluster.adoc @@ -92,7 +92,7 @@ You can create a cluster by using: . Create an Amazon EKS `IPv4` cluster with the Amazon EKS default Kubernetes version in your default {aws} Region. Before running command, make the following replacements: . Replace [.replaceable]`region-code` with the {aws} Region that you want to create your cluster in. . Replace [.replaceable]`my-cluster` with a name for your cluster. The name can contain only alphanumeric characters (case-sensitive) and hyphens. It must start with an alphanumeric character and can't be longer than 100 characters. The name must be unique within the {aws} Region and {aws} account that you're creating the cluster in. -. Replace [.replaceable]`{k8s-n}` with any eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported version,type="documentation"]. +. Replace [.replaceable]`{k8s-n}` with any link:eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported version,type="documentation"]. . Change the values for `vpc-private-subnets` to meet your requirements. You can also add additional IDs. You must specify at least two subnet IDs. If you'd rather specify public subnets, you can change `--vpc-private-subnets` to `--vpc-public-subnets`. Public subnets have an associated route table with a route to an internet gateway, but private subnets don't have an associated route table. We recommend using private subnets whenever possible. + The subnets that you choose must meet the <>. Before selecting subnets, we recommend that you're familiar with all of the <>. @@ -218,7 +218,7 @@ Cluster provisioning takes several minutes. + ** Replace [.replaceable]`region-code` with the {aws} Region that you want to create your cluster in. ** Replace [.replaceable]`my-cluster` with a name for your cluster. The name can contain only alphanumeric characters (case-sensitive), hyphens, and underscores. It must start with an alphanumeric character and can't be longer than 100 characters. The name must be unique within the {aws} Region and {aws} account that you're creating the cluster in. -** Replace [.replaceable]`{k8s-n}` with any eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported version,type="documentation"]. +** Replace [.replaceable]`{k8s-n}` with any link:eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported version,type="documentation"]. ** Replace [.replaceable]`111122223333` with your account ID and [.replaceable]`myAmazonEKSClusterRole` with the name of your cluster IAM role. ** Replace the values for `subnetIds` with your own. You can also add additional IDs. You must specify at least two subnet IDs. + diff --git a/latest/ug/clusters/update-cluster.adoc b/latest/ug/clusters/update-cluster.adoc index 7514474b..b648d374 100644 --- a/latest/ug/clusters/update-cluster.adoc +++ b/latest/ug/clusters/update-cluster.adoc @@ -15,7 +15,7 @@ When a new Kubernetes version is available in Amazon EKS, you can update your Am [IMPORTANT] ==== -Once you upgrade a cluster, you can't downgrade to a previous version. Before you update to a new Kubernetes version, we recommend that you review the information in eks/latest/userguide/kubernetes-versions.html[Understand the Kubernetes version lifecycle on EKS,type="documentation"] and the update steps in this topic. +Once you upgrade a cluster, you can't downgrade to a previous version. Before you update to a new Kubernetes version, we recommend that you review the information in link:eks/latest/userguide/kubernetes-versions.html[Understand the Kubernetes version lifecycle on EKS,type="documentation"] and the update steps in this topic. ==== @@ -127,7 +127,7 @@ eksctl version For instructions on how to install and update `eksctl`, see https://eksctl.io/installation[Installation] in the `eksctl` documentation. -Update the Kubernetes version of your Amazon EKS control plane. Replace `` with your cluster name. Replace `` with the Amazon EKS supported version number that you want to update your cluster to. For a list of supported version numbers, see eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"]. +Update the Kubernetes version of your Amazon EKS control plane. Replace `` with your cluster name. Replace `` with the Amazon EKS supported version number that you want to update your cluster to. For a list of supported version numbers, see link:eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"]. [source,bash,subs="verbatim,attributes"] ---- @@ -151,7 +151,7 @@ Continue to <>. === Update cluster - {aws} CLI . Verify that the {aws} CLI is installed and that you are logged in. For more information, see link:cli/latest/userguide/getting-started-install.html[Installing or updating to the latest version of the {aws} CLI,type="documentation"]. -. Update your Amazon EKS cluster with the following {aws} CLI command. Replace `` and `` of the cluster you want to upgrade. Replace `` with the Amazon EKS supported version number that you want to update your cluster to. For a list of supported version numbers, see eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"]. +. Update your Amazon EKS cluster with the following {aws} CLI command. Replace `` and `` of the cluster you want to upgrade. Replace `` with the Amazon EKS supported version number that you want to update your cluster to. For a list of supported version numbers, see link:eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"]. + [source,bash,subs="verbatim,attributes"] ---- diff --git a/latest/ug/manage-access/k8s-access/setting-up-access-entries.adoc b/latest/ug/manage-access/k8s-access/setting-up-access-entries.adoc index 3fdb4621..8e4268c9 100644 --- a/latest/ug/manage-access/k8s-access/setting-up-access-entries.adoc +++ b/latest/ug/manage-access/k8s-access/setting-up-access-entries.adoc @@ -49,4 +49,4 @@ To use _access entries_, the cluster must have a platform version that is the sa | `1.26` | `eks.11` |=== -For more information, see eks/latest/userguide/platform-versions.html[platform-versions,type="documentation"]. \ No newline at end of file +For more information, see link:eks/latest/userguide/platform-versions.html[platform-versions,type="documentation"]. \ No newline at end of file diff --git a/latest/ug/networking/deploy-ipv6-cluster.adoc b/latest/ug/networking/deploy-ipv6-cluster.adoc index ce146570..49498546 100644 --- a/latest/ug/networking/deploy-ipv6-cluster.adoc +++ b/latest/ug/networking/deploy-ipv6-cluster.adoc @@ -32,7 +32,7 @@ You can use the eksctl or CLI to deploy an `IPv6` cluster. + *** Replace [.replaceable]`my-cluster` with a name for your cluster. The name can contain only alphanumeric characters (case-sensitive) and hyphens. It must start with an alphanumeric character and can't be longer than 100 characters. The name must be unique within the {aws} Region and {aws} account that you're creating the cluster in. *** Replace [.replaceable]`region-code` with any {aws} Region that is supported by Amazon EKS. For a list of {aws} Regions, see link:general/latest/gr/eks.html[Amazon EKS endpoints and quotas,type="documentation"] in the {aws} General Reference guide. -*** The value for `version` with the version of your cluster. For more information, see eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"]. +*** The value for `version` with the version of your cluster. For more information, see link:eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"]. *** Replace [.replaceable]`my-nodegroup` with a name for your node group. The node group name can't be longer than 63 characters. It must start with letter or digit, but can also include hyphens and underscores for the remaining characters. *** Replace [.replaceable]`t3.medium` with any link:AWSEC2/latest/UserGuide/instance-types.html#ec2-nitro-instances[{aws} Nitro System instance type,type="documentation"]. + diff --git a/latest/ug/nodes/hybrid-nodes-cluster-create.adoc b/latest/ug/nodes/hybrid-nodes-cluster-create.adoc index e84da094..7e532453 100644 --- a/latest/ug/nodes/hybrid-nodes-cluster-create.adoc +++ b/latest/ug/nodes/hybrid-nodes-cluster-create.adoc @@ -10,7 +10,7 @@ include::../attributes.txt[] Create hybrid nodes cluster -- -This topic provides an overview of the available options and describes what to consider when you create a hybrid nodes-enabled Amazon EKS cluster. EKS Hybrid Nodes have the same eks/latest/userguide/kubernetes-versions.html[Kubernetes version support,type="documentation"] as Amazon EKS clusters with cloud nodes, including standard and extended support. +This topic provides an overview of the available options and describes what to consider when you create a hybrid nodes-enabled Amazon EKS cluster. EKS Hybrid Nodes have the same link:eks/latest/userguide/kubernetes-versions.html[Kubernetes version support,type="documentation"] as Amazon EKS clusters with cloud nodes, including standard and extended support. If you are not planning to use EKS Hybrid Nodes, see the primary Amazon EKS create cluster documentation at <>. @@ -96,7 +96,7 @@ You need to install the latest version of the `eksctl` command line tool. To ins . Create `cluster-config.yaml` to define a hybrid nodes-enabled Amazon EKS IPv4 cluster. Make the following replacements in your `cluster-config.yaml`. For a full list of settings, see the https://eksctl.io/getting-started/[eksctl documentation]. .. Replace `CLUSTER_NAME` with a name for your cluster. The name can contain only alphanumeric characters (case-sensitive) and hyphens. It must start with an alphanumeric character and can't be longer than 100 characters. The name must be unique within the {aws} Region and {aws} account that you're creating the cluster in. .. Replace `AWS_REGION` with the {aws} Region that you want to create your cluster in. -.. Replace `K8S_VERSION` with any eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported version,type="documentation"]. +.. Replace `K8S_VERSION` with any link:eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported version,type="documentation"]. .. Replace `CREDS_PROVIDER` with `ssm` or `ira` based on the credential provider you configured in the steps for <>. .. Replace `CA_BUNDLE_CERT` if your credential provider is set to `ira`, which uses {aws} IAM Roles Anywhere as the credential provider. The CA_BUNDLE_CERT is the certificate authority (CA) certificate body and depends on your choice of CA. The certificate must be in Privacy Enhanced Mail (PEM) format. .. Replace `GATEWAY_ID` with the ID of your virtual private gateway or transit gateway to be attached to your VPC. @@ -169,7 +169,7 @@ curl -OL 'https://raw.githubusercontent.com/aws/eks-hybrid/refs/heads/main/examp ... Not overlap with each other, the `VPC CIDR` for your cluster, or your Kubernetes service IPv4 CIDR. .. `CLUSTER_AUTH`: the cluster authentication mode for your cluster. Valid values are `API` and `API_AND_CONFIG_MAP`. The default in the template is `API_AND_CONFIG_MAP`. .. `CLUSTER_ENDPOINT`: the cluster endpoint connectivity for your cluster. Valid values are “Public” and “Private”. The default in the template is Private, which means you will only be able to connect to the Kubernetes API endpoint from within your VPC. -.. `K8S_VERSION`: the Kubernetes version to use for your cluster. See eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"]. +.. `K8S_VERSION`: the Kubernetes version to use for your cluster. See link:eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"]. + [source,json,subs="verbatim,attributes"] ---- diff --git a/latest/ug/nodes/hybrid-nodes-join.adoc b/latest/ug/nodes/hybrid-nodes-join.adoc index 9e5cb39e..7516682f 100644 --- a/latest/ug/nodes/hybrid-nodes-join.adoc +++ b/latest/ug/nodes/hybrid-nodes-join.adoc @@ -65,7 +65,7 @@ Run the command below to install the hybrid nodes dependencies on your on-premis The hybrid nodes CLI (`nodeadm`) must be run with a user that has sudo/root access on your host. ==== -* Replace `K8S_VERSION` with the Kubernetes minor version of your Amazon EKS cluster, for example `1.31`. See eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"] for a list of the supported Kubernetes versions. +* Replace `K8S_VERSION` with the Kubernetes minor version of your Amazon EKS cluster, for example `1.31`. See link:eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"] for a list of the supported Kubernetes versions. * Replace `CREDS_PROVIDER` with the on-premises credential provider you are using. Valid values are `ssm` for {aws} SSM and `iam-ra` for {aws} IAM Roles Anywhere. [source,bash,subs="verbatim,attributes,quotes"] diff --git a/latest/ug/nodes/hybrid-nodes-os.adoc b/latest/ug/nodes/hybrid-nodes-os.adoc index f535a3c0..f520f29a 100644 --- a/latest/ug/nodes/hybrid-nodes-os.adoc +++ b/latest/ug/nodes/hybrid-nodes-os.adoc @@ -65,7 +65,7 @@ The table below represents the operating system versions that are compatible and === ARM -* If you are using ARM hardware, an ARMv8.2 compliant processor with the Cryptography Extension (ARMv8.2+crypto) is required to run version 1.31 and above of the EKS kube-proxy add-on. All Raspberry Pi systems prior to the Raspberry Pi 5, as well as Cortex-A72 based processors, do not meet this requirement. As a workaround, you can continue to use version 1.30 of the EKS kube-proxy add-on until it reaches end of extended support in July of 2026, see eks/latest/userguide/kubernetes-versions.html[Kubernetes release calendar,type="documentation"], or use a custom kube-proxy image from upstream. +* If you are using ARM hardware, an ARMv8.2 compliant processor with the Cryptography Extension (ARMv8.2+crypto) is required to run version 1.31 and above of the EKS kube-proxy add-on. All Raspberry Pi systems prior to the Raspberry Pi 5, as well as Cortex-A72 based processors, do not meet this requirement. As a workaround, you can continue to use version 1.30 of the EKS kube-proxy add-on until it reaches end of extended support in July of 2026, see link:eks/latest/userguide/kubernetes-versions.html[Kubernetes release calendar,type="documentation"], or use a custom kube-proxy image from upstream. * The following error message in the kube-proxy log indicates this incompatibility: [source,none] ---- @@ -117,7 +117,7 @@ The following environment variables must be set for building images with all ope |K8S_VERSION |String -|Kubernetes version for hybrid nodes (for example `1.31`). For supported Kubernetes versions, see eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"]. +|Kubernetes version for hybrid nodes (for example `1.31`). For supported Kubernetes versions, see link:eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"]. |NODEADM_ARCH |String diff --git a/latest/ug/nodes/hybrid-nodes-upgrade.adoc b/latest/ug/nodes/hybrid-nodes-upgrade.adoc index 1620bb06..eb248846 100644 --- a/latest/ug/nodes/hybrid-nodes-upgrade.adoc +++ b/latest/ug/nodes/hybrid-nodes-upgrade.adoc @@ -10,7 +10,7 @@ include::../attributes.txt[] Upgrade Kubernetes versions on hybrid nodes -- -The guidance for upgrading hybrid nodes is similar to self-managed Amazon EKS nodes that run in Amazon EC2. We recommend that you create new hybrid nodes on your target Kubernetes version, gracefully migrate your existing applications to the hybrid nodes on the new Kubernetes version, and remove the hybrid nodes on the old Kubernetes version from your cluster. Be sure to review the link:eks/latest/best-practices/cluster-upgrades.html[Amazon EKS Best Practices,type="documentation"] for upgrades before initiating an upgrade. Amazon EKS Hybrid Nodes have the same eks/latest/userguide/kubernetes-versions.html[Kubernetes version support,type="documentation"] for Amazon EKS clusters with cloud nodes, including standard and extended support. +The guidance for upgrading hybrid nodes is similar to self-managed Amazon EKS nodes that run in Amazon EC2. We recommend that you create new hybrid nodes on your target Kubernetes version, gracefully migrate your existing applications to the hybrid nodes on the new Kubernetes version, and remove the hybrid nodes on the old Kubernetes version from your cluster. Be sure to review the link:eks/latest/best-practices/cluster-upgrades.html[Amazon EKS Best Practices,type="documentation"] for upgrades before initiating an upgrade. Amazon EKS Hybrid Nodes have the same link:eks/latest/userguide/kubernetes-versions.html[Kubernetes version support,type="documentation"] for Amazon EKS clusters with cloud nodes, including standard and extended support. Amazon EKS Hybrid Nodes follow the same https://kubernetes.io/releases/version-skew-policy/#supported-version-skew[version skew policy] for nodes as upstream Kubernetes. Amazon EKS Hybrid Nodes cannot be on a newer version than the Amazon EKS control plane, and hybrid nodes may be up to three Kubernetes minor versions older than the Amazon EKS control plane minor version. diff --git a/latest/ug/nodes/launch-workers.adoc b/latest/ug/nodes/launch-workers.adoc index 0ad83113..3fd6b3aa 100644 --- a/latest/ug/nodes/launch-workers.adoc +++ b/latest/ug/nodes/launch-workers.adoc @@ -121,7 +121,7 @@ The following steps show one operation to retrieve the applicable group. ** *NodeAutoScalingGroupDesiredCapacity*: Enter the desired number of nodes to scale to when your stack is created. ** *NodeAutoScalingGroupMaxSize*: Enter the maximum number of nodes that your node Auto Scaling group can scale out to. ** *NodeInstanceType*: Choose an instance type for your nodes. For more information, see <>. -** *NodeImageIdSSMParam*: Pre-populated with the Amazon EC2 Systems Manager parameter of a recent Amazon EKS optimized AMI for a variable Kubernetes version. To use a different Kubernetes minor version supported with Amazon EKS, replace [.replaceable]`1.XX` with a different eks/latest/userguide/kubernetes-versions.html[supported version,type="documentation"]. We recommend specifying the same Kubernetes version as your cluster. +** *NodeImageIdSSMParam*: Pre-populated with the Amazon EC2 Systems Manager parameter of a recent Amazon EKS optimized AMI for a variable Kubernetes version. To use a different Kubernetes minor version supported with Amazon EKS, replace [.replaceable]`1.XX` with a different link:eks/latest/userguide/kubernetes-versions.html[supported version,type="documentation"]. We recommend specifying the same Kubernetes version as your cluster. + You can also replace [.replaceable]`amazon-linux-2` with a different AMI type. For more information, see <>. + diff --git a/latest/ug/nodes/retrieve-ami-id-bottlerocket.adoc b/latest/ug/nodes/retrieve-ami-id-bottlerocket.adoc index 36e8ff6e..e6a7b680 100644 --- a/latest/ug/nodes/retrieve-ami-id-bottlerocket.adoc +++ b/latest/ug/nodes/retrieve-ami-id-bottlerocket.adoc @@ -14,7 +14,7 @@ When deploying nodes, you can specify an ID for a pre-built Amazon EKS optimized You can retrieve the image ID of the latest recommended Amazon EKS optimized Bottlerocket AMI with the following {aws} CLI command, which uses the sub-parameter `image_id`. Make the following modifications to the command as needed and then run the modified command: -* Replace [.replaceable]`kubernetes-version` with a supported eks/latest/userguide/platform-versions.html[platform-version,type="documentation"]. +* Replace [.replaceable]`kubernetes-version` with a supported link:eks/latest/userguide/platform-versions.html[platform-version,type="documentation"]. * Replace [.replaceable]`-flavor` with one of the following options. + ** Remove [.replaceable]`-flavor` for variants without a GPU. diff --git a/latest/ug/nodes/retrieve-ami-id.adoc b/latest/ug/nodes/retrieve-ami-id.adoc index d8136140..405e2871 100644 --- a/latest/ug/nodes/retrieve-ami-id.adoc +++ b/latest/ug/nodes/retrieve-ami-id.adoc @@ -14,7 +14,7 @@ When deploying nodes, you can specify an ID for a pre-built Amazon EKS optimized You can retrieve the image ID of the latest recommended Amazon EKS optimized Amazon Linux AMI with the following command, which uses the sub-parameter `image_id`. Make the following modifications to the command as needed and then run the modified command: -* Replace `` with a supported eks/latest/userguide/platform-versions.html[platform-version,type="documentation"]. +* Replace `` with an link:eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported version,type="documentation"]. * Replace [.replaceable]`ami-type` with one of the following options. For information about the types of Amazon EC2 instances, see link:AWSEC2/latest/UserGuide/instance-types.html[Amazon EC2 instance types,type="documentation"]. + ** Use [.replaceable]`amazon-linux-2023/x86_64/standard` for Amazon Linux 2023 (AL2023) `x86` based instances. diff --git a/latest/ug/nodes/retrieve-windows-ami-id.adoc b/latest/ug/nodes/retrieve-windows-ami-id.adoc index 83cb66b4..424b7750 100644 --- a/latest/ug/nodes/retrieve-windows-ami-id.adoc +++ b/latest/ug/nodes/retrieve-windows-ami-id.adoc @@ -22,7 +22,7 @@ You can retrieve the image ID of the latest recommended Amazon EKS optimized Win + ** Use [.replaceable]`Core` for a minimal installation with a smaller attack surface. ** Use [.replaceable]`Full` to include the Windows desktop experience. -* Replace [.replaceable]`kubernetes-version` with a supported eks/latest/userguide/platform-versions.html[platform-version,type="documentation"]. +* Replace [.replaceable]`kubernetes-version` with a supported link:eks/latest/userguide/platform-versions.html[platform-version,type="documentation"]. * Replace [.replaceable]`region-code` with an link:general/latest/gr/eks.html[Amazon EKS supported {aws} Region,type="documentation"] for which you want the AMI ID. [source,bash,subs="verbatim,attributes,quotes"] diff --git a/latest/ug/nodes/update-stack.adoc b/latest/ug/nodes/update-stack.adoc index 12864aee..e990da96 100644 --- a/latest/ug/nodes/update-stack.adoc +++ b/latest/ug/nodes/update-stack.adoc @@ -83,7 +83,7 @@ IMPORTANT: Some instance types might not be available in all {aws} Regions. /aws/service/eks/optimized-ami/{k8s-n}/amazon-linux-2/recommended/image_id ---- + -You can replace [.replaceable]`{k8s-n}` with a eks/latest/userguide/platform-versions.html[platform-version,type="documentation"] that's the same. Or, it should be up to one version earlier than the Kubernetes version running on your control plane. We recommend that you keep your nodes at the same version as your control plane. You can also replace [.replaceable]`amazon-linux-2` with a different AMI type. For more information, see <>. +You can replace [.replaceable]`{k8s-n}` with a link:eks/latest/userguide/platform-versions.html[platform-version,type="documentation"] that's the same. Or, it should be up to one version earlier than the Kubernetes version running on your control plane. We recommend that you keep your nodes at the same version as your control plane. You can also replace [.replaceable]`amazon-linux-2` with a different AMI type. For more information, see <>. + NOTE: Using the Amazon EC2 Systems Manager parameter enables you to update your nodes in the future without having to look up and specify an AMI ID. If your {aws} CloudFormation stack is using this value, any stack update always launches the latest recommended Amazon EKS optimized AMI for your specified Kubernetes version. This is even the case even if you don't change any values in the template. ** *NodeImageId* – To use your own custom AMI, enter the ID for the AMI to use. diff --git a/latest/ug/outposts/eks-outposts-self-managed-nodes.adoc b/latest/ug/outposts/eks-outposts-self-managed-nodes.adoc index 6bf6d2fd..f298a359 100644 --- a/latest/ug/outposts/eks-outposts-self-managed-nodes.adoc +++ b/latest/ug/outposts/eks-outposts-self-managed-nodes.adoc @@ -100,7 +100,7 @@ The following steps show one operation to retrieve the applicable group. ** *NodeAutoScalingGroupDesiredCapacity*: Enter the desired number of nodes to scale to when your stack is created. ** *NodeAutoScalingGroupMaxSize*: Enter the maximum number of nodes that your node Auto Scaling group can scale out to. ** *NodeInstanceType*: Choose an instance type for your nodes. If your cluster is running on the {aws} Cloud, then for more information, see <>. If your cluster is running on an Outpost, then you can only select an instance type that is available on your Outpost. -** *NodeImageIdSSMParam*: Pre-populated with the Amazon EC2 Systems Manager parameter of a recent Amazon EKS optimized AMI for a variable Kubernetes version. To use a different Kubernetes minor version supported with Amazon EKS, replace [.replaceable]`1.XX` with a different eks/latest/userguide/kubernetes-versions.html[supported version,type="documentation"]. We recommend specifying the same Kubernetes version as your cluster. +** *NodeImageIdSSMParam*: Pre-populated with the Amazon EC2 Systems Manager parameter of a recent Amazon EKS optimized AMI for a variable Kubernetes version. To use a different Kubernetes minor version supported with Amazon EKS, replace [.replaceable]`1.XX` with a different link:eks/latest/userguide/kubernetes-versions.html[supported version,type="documentation"]. We recommend specifying the same Kubernetes version as your cluster. + To use an Amazon EKS optimized accelerated AMI, replace [.replaceable]`amazon-linux-2` with `amazon-linux-2-gpu`. To use an Amazon EKS optimized Arm AMI, replace [.replaceable]`amazon-linux-2` with `amazon-linux-2-arm64`. + diff --git a/latest/ug/outposts/eks-outposts.adoc b/latest/ug/outposts/eks-outposts.adoc index 0a8d1a1e..1df3b6ba 100644 --- a/latest/ug/outposts/eks-outposts.adoc +++ b/latest/ug/outposts/eks-outposts.adoc @@ -63,7 +63,7 @@ The following table compares the differences between the two options. |eks/latest/userguide/kubernetes-versions.html[Supported Amazon EKS versions,type="documentation"]. |Platform versions -|See eks/latest/userguide/platform-versions.html[EKS platform-versions,type="documentation"] +|See link:eks/latest/userguide/platform-versions.html[EKS platform-versions,type="documentation"] |See <> |Outpost form factors diff --git a/latest/ug/security/configuration-vulnerability-analysis.adoc b/latest/ug/security/configuration-vulnerability-analysis.adoc index 314bc2d7..93b82271 100644 --- a/latest/ug/security/configuration-vulnerability-analysis.adoc +++ b/latest/ug/security/configuration-vulnerability-analysis.adoc @@ -29,9 +29,9 @@ For an automated `aws-sample` pipeline to update your node group with a CIS benc [#configuration-vulnerability-analysis-pv] == Amazon EKS platform versions -Amazon EKS _platform versions_ represent the capabilities of the cluster control plane, including which Kubernetes API server flags are enabled and the current Kubernetes patch version. New clusters are deployed with the latest platform version. For details, see eks/latest/userguide/platform-versions.html[EKS platform-versions,type="documentation"]. +Amazon EKS _platform versions_ represent the capabilities of the cluster control plane, including which Kubernetes API server flags are enabled and the current Kubernetes patch version. New clusters are deployed with the latest platform version. For details, see link:eks/latest/userguide/platform-versions.html[EKS platform-versions,type="documentation"]. -You can <> to newer Kubernetes versions. As new Kubernetes versions become available in Amazon EKS, we recommend that you proactively update your clusters to use the latest available version. For more information about Kubernetes versions in EKS, see eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"]. +You can <> to newer Kubernetes versions. As new Kubernetes versions become available in Amazon EKS, we recommend that you proactively update your clusters to use the latest available version. For more information about Kubernetes versions in EKS, see link:eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"]. [#configuration-vulnerability-analysis-os] == Operating system vulnerability list diff --git a/latest/ug/storage/efs-csi.adoc b/latest/ug/storage/efs-csi.adoc index e525721b..4b2ddfe1 100644 --- a/latest/ug/storage/efs-csi.adoc +++ b/latest/ug/storage/efs-csi.adoc @@ -17,7 +17,7 @@ link:efs/latest/ug/whatisefs.html[Amazon Elastic File System,type="documentation * The Amazon EFS CSI driver isn't compatible with Windows-based container images. * You can't use https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/examples/kubernetes/dynamic_provisioning/README.md[dynamic provisioning] for persistent volumes with Fargate nodes, but you can use https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/examples/kubernetes/static_provisioning/README.md[static provisioning]. -* https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/examples/kubernetes/dynamic_provisioning/README.md[Dynamic provisioning] requires https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/CHANGELOG-1.x.md#v12[1.2] or later of the driver. You can use https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/examples/kubernetes/static_provisioning/README.md[static provisioning] for persistent volumes using version `1.1` of the driver on any supported Amazon EKS cluster version (see eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"]). +* https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/examples/kubernetes/dynamic_provisioning/README.md[Dynamic provisioning] requires https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/CHANGELOG-1.x.md#v12[1.2] or later of the driver. You can use https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/examples/kubernetes/static_provisioning/README.md[static provisioning] for persistent volumes using version `1.1` of the driver on any supported Amazon EKS cluster version (see link:eks/latest/userguide/kubernetes-versions.html[Amazon EKS supported versions,type="documentation"]). * Version https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/CHANGELOG-1.x.md#v132[1.3.2] or later of this driver supports the Arm64 architecture, including Amazon EC2 Graviton-based instances. * Version https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/CHANGELOG-1.x.md#v142[1.4.2] or later of this driver supports using FIPS for mounting file systems. * Take note of the resource quotas for Amazon EFS. For example, there's a quota of 1000 access points that can be created for each Amazon EFS file system. For more information, see link:efs/latest/ug/limits.html#limits-efs-resources-per-account-per-region[Amazon EFS resource quotas that you cannot change,type="documentation"]. diff --git a/latest/ug/troubleshooting/troubleshooting.adoc b/latest/ug/troubleshooting/troubleshooting.adoc index fe046232..e07454ac 100644 --- a/latest/ug/troubleshooting/troubleshooting.adoc +++ b/latest/ug/troubleshooting/troubleshooting.adoc @@ -479,7 +479,7 @@ You can identify all existing Pods in your cluster that are using stale tokens. [#troubleshooting-platform-version] == Amazon EKS platform version is more than two versions behind the current platform version -This can happen when Amazon EKS isn't able to automatically update your cluster's eks/latest/userguide/platform-versions.html[platform-version,type="documentation"]. Though there are many causes for this, some of the common causes follow. If any of these problems apply to your cluster, it may still function, its platform version just won't be updated by Amazon EKS. +This can happen when Amazon EKS isn't able to automatically update your cluster's link:eks/latest/userguide/platform-versions.html[platform-version,type="documentation"]. Though there are many causes for this, some of the common causes follow. If any of these problems apply to your cluster, it may still function, its platform version just won't be updated by Amazon EKS. .Problem The <> was deleted – This role was specified when the cluster was created. You can see which role was specified with the following command. Replace [.replaceable]`my-cluster` with the name of your cluster. diff --git a/latest/ug/versioning/view-support-status.adoc b/latest/ug/versioning/view-support-status.adoc index 3480efa5..da5bd397 100644 --- a/latest/ug/versioning/view-support-status.adoc +++ b/latest/ug/versioning/view-support-status.adoc @@ -7,7 +7,7 @@ include::../attributes.txt[] The *cluster support period* section of the {aws} console indicates if your cluster is _currently_ on standard or extended support. If your cluster support period is *Extended support*, you are being charged for EKS extended support. -For more information about standard and extended support, see eks/latest/userguide/kubernetes-versions.html[Understand the Kubernetes version lifecycle on EKS,type="documentation"]. +For more information about standard and extended support, see link:eks/latest/userguide/kubernetes-versions.html[Understand the Kubernetes version lifecycle on EKS,type="documentation"]. . Navigate to the *Clusters* page in the EKS section of the {aws} Console. Confirm the console is set to the same {aws} region as the cluster you want to review. . Review the *Support Period* column. If the value is *Standard support until...*, you are not currently being charged for extended support. You are within the standard support period. If the value is *Extended support...* this cluster is currently being charged for extended support.