Skip to content

Commit cd5f3c1

Browse files
committed
build remediation: fix leading underscore in create_addon_console id
1 parent e912cd4 commit cd5f3c1

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

latest/ug/clusters/create-cluster-auto.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ When you're done with this page, choose *Next*.
106106
** When you're done with this page, choose *Next*.
107107
. On the *Configure selected add-ons settings* page, select the version that you want to install. You can always update to a later version after cluster creation.
108108
+
109-
For add-ons that support EKS Pod Identities, you can use the console to automatically generate the role with the name, {aws} managed policy, and trust policy prepopulated specifically for the add-on. You can re-use existing roles or create new roles for supported add-ons. For the steps to use the console to create roles for add-ons that support EKS Pod Identities, see <<_create_add_on_console>>. If an add-on does not support EKS Pod Identity, a message displays with instructions to use the wizard to create the IAM roles for service accounts (IRSA) after the cluster is created.
109+
For add-ons that support EKS Pod Identities, you can use the console to automatically generate the role with the name, {aws} managed policy, and trust policy prepopulated specifically for the add-on. You can re-use existing roles or create new roles for supported add-ons. For the steps to use the console to create roles for add-ons that support EKS Pod Identities, see <<create_add_on_console>>. If an add-on does not support EKS Pod Identity, a message displays with instructions to use the wizard to create the IAM roles for service accounts (IRSA) after the cluster is created.
110110
+
111111
You can update the configuration of each add-on after cluster creation. For more information about configuring add-ons, see <<updating-an-add-on>>. When you're done with this page, choose *Next*.
112112
. On the *Review and create* page, review the information that you entered or selected on the previous pages. If you need to make changes, choose *Edit*. When you're satisfied, choose *Create*. The *Status* field shows *CREATING* while the cluster is provisioned.
@@ -311,4 +311,4 @@ aws eks describe-cluster --region region-code --name my-cluster --query "cluster
311311
* <<access-entries>>
312312
* <<enable-kms,Enable secrets encryption for your cluster>>.
313313
* <<control-plane-logs,Configure logging for your cluster>>.
314-
* <<eks-compute,Add nodes to your cluster>>.
314+
* <<eks-compute,Add nodes to your cluster>>.

latest/ug/clusters/create-cluster.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -189,7 +189,7 @@ When you're done with this page, choose *Next*.
189189
Some add-ons, such as Amazon VPC CNI, CoreDNS, and kube-proxy, are installed by default. If you disable any of the default add-ons, this may affect your ability to run Kubernetes applications.
190190
. On the *Configure selected add-ons settings* page, select the version that you want to install. You can always update to a later version after cluster creation.
191191
+
192-
For add-ons that support EKS Pod Identities, you can use the console to automatically generate the role with the name, {aws} managed policy, and trust policy prepopulated specifically for the add-on. You can re-use existing roles or create new roles for supported add-ons. For the steps to use the console to create roles for add-ons that support EKS Pod Identities, see <<_create_add_on_console>>. If an add-on does not support EKS Pod Identity, a message displays with instructions to use the wizard to create the IAM roles for service accounts (IRSA) after the cluster is created.
192+
For add-ons that support EKS Pod Identities, you can use the console to automatically generate the role with the name, {aws} managed policy, and trust policy prepopulated specifically for the add-on. You can re-use existing roles or create new roles for supported add-ons. For the steps to use the console to create roles for add-ons that support EKS Pod Identities, see <<create_add_on_console>>. If an add-on does not support EKS Pod Identity, a message displays with instructions to use the wizard to create the IAM roles for service accounts (IRSA) after the cluster is created.
193193
+
194194
You can update the configuration of each add-on after cluster creation. For more information about configuring add-ons, see <<updating-an-add-on>>. When you're done with this page, choose *Next*.
195195
. On the *Review and create* page, review the information that you entered or selected on the previous pages. If you need to make changes, choose *Edit*. When you're satisfied, choose *Create*. The *Status* field shows *CREATING* while the cluster is provisioned.

latest/ug/workloads/creating-an-add-on.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ eksctl create addon --help
121121
+
122122
For more information about available options see https://eksctl.io/usage/addons/[Addons] in the `eksctl` documentation.
123123

124-
[#_create_add_on_console]
124+
[#create_add_on_console]
125125
== Create add-on ({aws} Console)
126126

127127
. Open the link:eks/home#/clusters[Amazon EKS console,type="console"].
@@ -327,4 +327,4 @@ For a full list of available options, see `link:cli/latest/reference/eks/create-
327327
328328
----
329329
+
330-
If you receive an error similar to the error in the previous output, visit the URL in the output of a previous step to subscribe to the add-on. Once subscribed, run the `create-addon` command again.
330+
If you receive an error similar to the error in the previous output, visit the URL in the output of a previous step to subscribe to the add-on. Once subscribed, run the `create-addon` command again.

0 commit comments

Comments
 (0)