Bump LBC version to 2.13.3, use /latest/ in links.

fincd-aws · fincd-aws · commit c6f703cdfa25 · 2025-07-16T16:09:00.000-07:00
diff --git a/latest/ug/networking/aws-load-balancer-controller.adoc b/latest/ug/networking/aws-load-balancer-controller.adoc
@@ -19,11 +19,11 @@ The controller watches for Kubernetes Ingress or Service resources. In response,
 The controller provisions the following resources: 
 
 *Kubernetes `Ingress`*::
-The LBC creates an link:elasticloadbalancing/latest/application/introduction.html[{aws} Application Load Balancer (ALB),type="documentation"] when you create a Kubernetes `Ingress`. https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.7/guide/ingress/annotations/[Review the annotations you can apply to an Ingress resource.]
+The LBC creates an link:elasticloadbalancing/latest/application/introduction.html[{aws} Application Load Balancer (ALB),type="documentation"] when you create a Kubernetes `Ingress`. https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/ingress/annotations/[Review the annotations you can apply to an Ingress resource.]
 
 
 *Kubernetes service of the `LoadBalancer` type*::
-The LBC creates an link:elasticloadbalancing/latest/network/introduction.html[{aws} Network Load Balancer (NLB),type="documentation"]when you create a Kubernetes service of type `LoadBalancer`. https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.7/guide/service/annotations/[Review the annotations you can apply to a Service resource.]
+The LBC creates an link:elasticloadbalancing/latest/network/introduction.html[{aws} Network Load Balancer (NLB),type="documentation"]when you create a Kubernetes service of type `LoadBalancer`. https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/service/annotations/[Review the annotations you can apply to a Service resource.]
 +
 In the past, the Kubernetes network load balancer was used for _instance_ targets, but the LBC was used for _IP_ targets. With the {aws} Load Balancer Controller version `2.3.0` or later, you can create NLBs using either target type. For more information about NLB target types, see link:elasticloadbalancing/latest/network/load-balancer-target-groups.html#target-type[Target type,type="documentation"] in the User Guide for Network Load Balancers.
 
@@ -62,7 +62,7 @@ Kubernetes includes a legacy cloud provider for {aws}. The legacy cloud provider
 [IMPORTANT]
 ====
 
-In versions 2.5 and newer, the {aws} Load Balancer Controller becomes the default controller for Kubernetes _service_ resources with the `type: LoadBalancer` and makes an {aws} Network Load Balancer (NLB) for each service. It does this by making a mutating webhook for services, which sets the `spec.loadBalancerClass` field to `service.k8s.aws/nlb` for new services of `type: LoadBalancer`. You can turn off this feature and revert to using the https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.7/guide/service/annotations/#legacy-cloud-provider[legacy Cloud Provider] as the default controller, by setting the helm chart value `enableServiceMutatorWebhook` to `false`. The cluster won't provision new Classic Load Balancers for your services unless you turn off this feature. Existing Classic Load Balancers will continue to work.
+In versions 2.5 and newer, the {aws} Load Balancer Controller becomes the default controller for Kubernetes _service_ resources with the `type: LoadBalancer` and makes an {aws} Network Load Balancer (NLB) for each service. It does this by making a mutating webhook for services, which sets the `spec.loadBalancerClass` field to `service.k8s.aws/nlb` for new services of `type: LoadBalancer`. You can turn off this feature and revert to using the https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/service/annotations/#legacy-cloud-provider[legacy Cloud Provider] as the default controller, by setting the helm chart value `enableServiceMutatorWebhook` to `false`. The cluster won't provision new Classic Load Balancers for your services unless you turn off this feature. Existing Classic Load Balancers will continue to work.
 
 ====
 
diff --git a/latest/ug/networking/lbc-helm.adoc b/latest/ug/networking/lbc-helm.adoc
@@ -43,13 +43,13 @@ Before proceeding with the configuration steps on this page, consider the follow
 
 [#lbc-helm-iam]
 == Step 1: Create IAM Role using `eksctl`
-The following steps refer to the {aws} Load Balancer Controller *v2.13.0* release version. For more information about all releases, see the https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/[{aws} Load Balancer Controller Release Page] on GitHub.
+The following steps refer to the {aws} Load Balancer Controller *v2.13.3* release version. For more information about all releases, see the https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/[{aws} Load Balancer Controller Release Page] on GitHub.
 
 . Download an IAM policy for the {aws} Load Balancer Controller that allows it to make calls to {aws} APIs on your behalf. 
 +
 [source,shell,subs="verbatim,attributes"]
 ----
-curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.0/docs/install/iam_policy.json
+curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/install/iam_policy.json
 ----
 ** If you are a non-standard {aws} partition, such as a Government or China region, https://github.com/kubernetes-sigs/aws-load-balancer-controller/tree/main/docs/install[review the policies on GitHub] and download the appropriate policy for your region.  
 . Create an IAM policy using the policy downloaded in the previous step. 
diff --git a/latest/ug/networking/lbc-manifest.adoc b/latest/ug/networking/lbc-manifest.adoc
@@ -43,7 +43,7 @@ Before proceeding with the configuration steps on this page, consider the follow
 
 [#lbc-iam]
 == Step 1: Configure IAM
-The following steps refer to the {aws} Load Balancer Controller *v2.11.0* release version. For more information about all releases, see the https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/[{aws} Load Balancer Controller Release Page] on GitHub.
+The following steps refer to the {aws} Load Balancer Controller *v2.13.3* release version. For more information about all releases, see the https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/[{aws} Load Balancer Controller Release Page] on GitHub.
 
 . Download an IAM policy for the {aws} Load Balancer Controller that allows it to make calls to {aws} APIs on your behalf.  
 +
@@ -53,15 +53,15 @@ The following steps refer to the {aws} Load Balancer Controller *v2.11.0* releas
 +
 [source,shell,subs="verbatim,attributes"]
 ----
-curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.11.0/docs/install/iam_policy.json
+curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/install/iam_policy.json
 ----
 
 
 {aws} GovCloud (US):::
 +
 [source,shell,subs="verbatim,attributes"]
 ----
-curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.11.0/docs/install/iam_policy_us-gov.json
+curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/install/iam_policy_us-gov.json
 ----
 +
 [source,shell,subs="verbatim,attributes"]
@@ -240,15 +240,15 @@ kubectl apply \
 +
 [source,bash,subs="verbatim,attributes"]
 ----
-curl -Lo v2_11_0_full.yaml https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.11.0/v2_11_0_full.yaml
+curl -Lo v2_13_3_full.yaml https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.13.3/v2_13_3_full.yaml
 ----
 . Make the following edits to the file.
 +
-.. If you downloaded the `v2_11_0_full.yaml` file, run the following command to remove the `ServiceAccount` section in the manifest. If you don't remove this section, the required annotation that you made to the service account in a previous step is overwritten. Removing this section also preserves the service account that you created in a previous step if you delete the controller.
+.. If you downloaded the `v2_13_3_full.yaml` file, run the following command to remove the `ServiceAccount` section in the manifest. If you don't remove this section, the required annotation that you made to the service account in a previous step is overwritten. Removing this section also preserves the service account that you created in a previous step if you delete the controller.
 +
 [source,shell,subs="verbatim,attributes"]
 ----
-sed -i.bak -e '690,698d' ./v2_11_0_full.yaml
+sed -i.bak -e '690,698d' ./v2_13_3_full.yaml
 ----
 +
 If you downloaded a different file version, then open the file in an editor and remove the following lines.  
@@ -269,20 +269,20 @@ metadata:
 +
 [source,shell,subs="verbatim,attributes"]
 ----
-sed -i.bak -e 's|your-cluster-name|my-cluster|' ./v2_11_0_full.yaml
+sed -i.bak -e 's|your-cluster-name|my-cluster|' ./v2_13_3_full.yaml
 ----
 .. If your nodes don't have access to the Amazon EKS Amazon ECR image repositories, then you need to pull the following image and push it to a repository that your nodes have access to. For more information on how to pull, tag, and push an image to your own repository, see <<copy-image-to-repository>>.
 +
 [source,bash,subs="verbatim,attributes"]
 ----
-public.ecr.aws/eks/aws-load-balancer-controller:v2.11.0
+public.ecr.aws/eks/aws-load-balancer-controller:v2.13.3
 ----
 +
 Add your registry's name to the manifest. The following command assumes that your private repository's name is the same as the source repository and adds your private registry's name to the file. Replace [.replaceable]`111122223333.dkr.ecr.region-code.amazonaws.com` with your registry. This line assumes that you named your private repository the same as the source repository. If not, change the `eks/aws-load-balancer-controller` text after your private registry name to your repository name.
 +
 [source,shell,subs="verbatim,attributes"]
 ----
-sed -i.bak -e 's|public.ecr.aws/eks/aws-load-balancer-controller|111122223333.dkr.ecr.region-code.amazonaws.com/eks/aws-load-balancer-controller|' ./v2_11_0_full.yaml
+sed -i.bak -e 's|public.ecr.aws/eks/aws-load-balancer-controller|111122223333.dkr.ecr.region-code.amazonaws.com/eks/aws-load-balancer-controller|' ./v2_13_3_full.yaml
 ----
 .. (Required only for Fargate or Restricted IMDS) 
 +
@@ -306,19 +306,19 @@ spec:
 +
 [source,shell,subs="verbatim,attributes"]
 ----
-kubectl apply -f v2_11_0_full.yaml
+kubectl apply -f v2_13_3_full.yaml
 ----
 . Download the `IngressClass` and `IngressClassParams` manifest to your cluster.
 +
 [source,shell,subs="verbatim,attributes"]
 ----
-curl -Lo v2_11_0_ingclass.yaml https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.11.0/v2_11_0_ingclass.yaml
+curl -Lo v2_13_3_ingclass.yaml https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.13.3/v2_13_3_ingclass.yaml
 ----
 . Apply the manifest to your cluster.
 +
 [source,shell,subs="verbatim,attributes"]
 ----
-kubectl apply -f v2_11_0_ingclass.yaml
+kubectl apply -f v2_13_3_ingclass.yaml
 ----
 
 
diff --git a/latest/ug/networking/lbc-remove.adoc b/latest/ug/networking/lbc-remove.adoc
@@ -87,7 +87,7 @@ To migrate from the ALB Ingress Controller for Kubernetes to the {aws} Load Bala
 +
 [source,shell,subs="verbatim,attributes"]
 ----
-curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.11.0/docs/install/iam_policy_v1_to_v2_additional.json
+curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/install/iam_policy_v1_to_v2_additional.json
 ----
 . If your cluster is in the {aws} GovCloud (US-East) or {aws} GovCloud (US-West) {aws} Regions, then replace `{arn-aws}` with `arn:aws-us-gov:`.
 +
diff --git a/latest/ug/workloads/alb-ingress.adoc b/latest/ug/workloads/alb-ingress.adoc
@@ -164,7 +164,7 @@ eksctl create fargateprofile \
 +
 [source,bash,subs="verbatim,attributes"]
 ----
-kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.11.0/docs/examples/2048/2048_full.yaml
+kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/examples/2048/2048_full.yaml
 ----
 *** *Private*::
 
@@ -173,7 +173,7 @@ kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-bala
 +
 [source,bash,subs="verbatim,attributes"]
 ----
-curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.11.0/docs/examples/2048/2048_full.yaml
+curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/examples/2048/2048_full.yaml
 ----
 .... Edit the file and find the line that says `alb.ingress.kubernetes.io/scheme: internet-facing`.
 .... Change [.replaceable]`internet-facing` to `internal` and save the file.
@@ -189,7 +189,7 @@ kubectl apply -f 2048_full.yaml
 +
 [source,bash,subs="verbatim,attributes"]
 ----
-curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.11.0/docs/examples/2048/2048_full.yaml
+curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/examples/2048/2048_full.yaml
 ----
 ... Open the file in an editor and add the following line to the annotations in the ingress spec.
 +
@@ -237,7 +237,7 @@ image::images/2048.png[2048 sample application,scaledwidth=100%]
 +
 [source,bash,subs="verbatim,attributes"]
 ----
-kubectl delete -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.11.0/docs/examples/2048/2048_full.yaml
+kubectl delete -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/examples/2048/2048_full.yaml
 ----
 ** If you downloaded and edited the manifest, use the following command.
 +

Original file line number	Diff line number	Diff line change
`@@ -43,7 +43,7 @@ Before proceeding with the configuration steps on this page, consider the follow`
`43`	`43`
`44`	`44`	`[#lbc-iam]`
`45`	`45`	`== Step 1: Configure IAM`
`46`		`-The following steps refer to the {aws} Load Balancer Controller v2.11.0 release version. For more information about all releases, see the https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/[{aws} Load Balancer Controller Release Page] on GitHub.`
	`46`	`+The following steps refer to the {aws} Load Balancer Controller v2.13.3 release version. For more information about all releases, see the https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/[{aws} Load Balancer Controller Release Page] on GitHub.`
`47`	`47`
`48`	`48`	`. Download an IAM policy for the {aws} Load Balancer Controller that allows it to make calls to {aws} APIs on your behalf.`
`49`	`49`	`+`
`@@ -53,15 +53,15 @@ The following steps refer to the {aws} Load Balancer Controller v2.11.0 releas`
`53`	`53`	`+`
`54`	`54`	`[source,shell,subs="verbatim,attributes"]`
`55`	`55`	`----`
`56`		`-curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.11.0/docs/install/iam_policy.json`
	`56`	`+curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/install/iam_policy.json`
`57`	`57`	`----`
`58`	`58`
`59`	`59`
`60`	`60`	`{aws} GovCloud (US):::`
`61`	`61`	`+`
`62`	`62`	`[source,shell,subs="verbatim,attributes"]`
`63`	`63`	`----`
`64`		`-curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.11.0/docs/install/iam_policy_us-gov.json`
	`64`	`+curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/install/iam_policy_us-gov.json`
`65`	`65`	`----`
`66`	`66`	`+`
`67`	`67`	`[source,shell,subs="verbatim,attributes"]`
`@@ -240,15 +240,15 @@ kubectl apply \`
`240`	`240`	`+`
`241`	`241`	`[source,bash,subs="verbatim,attributes"]`
`242`	`242`	`----`
`243`		`-curl -Lo v2_11_0_full.yaml https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.11.0/v2_11_0_full.yaml`
	`243`	`+curl -Lo v2_13_3_full.yaml https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.13.3/v2_13_3_full.yaml`
`244`	`244`	`----`
`245`	`245`	`. Make the following edits to the file.`
`246`	`246`	`+`
`247`		-.. If you downloaded the `v2_11_0_full.yaml` file, run the following command to remove the `ServiceAccount` section in the manifest. If you don't remove this section, the required annotation that you made to the service account in a previous step is overwritten. Removing this section also preserves the service account that you created in a previous step if you delete the controller.
	`247`	+.. If you downloaded the `v2_13_3_full.yaml` file, run the following command to remove the `ServiceAccount` section in the manifest. If you don't remove this section, the required annotation that you made to the service account in a previous step is overwritten. Removing this section also preserves the service account that you created in a previous step if you delete the controller.
`248`	`248`	`+`
`249`	`249`	`[source,shell,subs="verbatim,attributes"]`
`250`	`250`	`----`
`251`		`-sed -i.bak -e '690,698d' ./v2_11_0_full.yaml`
	`251`	`+sed -i.bak -e '690,698d' ./v2_13_3_full.yaml`
`252`	`252`	`----`
`253`	`253`	`+`
`254`	`254`	`If you downloaded a different file version, then open the file in an editor and remove the following lines.`
`@@ -269,20 +269,20 @@ metadata:`
`269`	`269`	`+`
`270`	`270`	`[source,shell,subs="verbatim,attributes"]`
`271`	`271`	`----`
`272`		`-sed -i.bak -e 's\|your-cluster-name\|my-cluster\|' ./v2_11_0_full.yaml`
	`272`	`+sed -i.bak -e 's\|your-cluster-name\|my-cluster\|' ./v2_13_3_full.yaml`
`273`	`273`	`----`
`274`	`274`	`.. If your nodes don't have access to the Amazon EKS Amazon ECR image repositories, then you need to pull the following image and push it to a repository that your nodes have access to. For more information on how to pull, tag, and push an image to your own repository, see <<copy-image-to-repository>>.`
`275`	`275`	`+`
`276`	`276`	`[source,bash,subs="verbatim,attributes"]`
`277`	`277`	`----`
`278`		`-public.ecr.aws/eks/aws-load-balancer-controller:v2.11.0`
	`278`	`+public.ecr.aws/eks/aws-load-balancer-controller:v2.13.3`
`279`	`279`	`----`
`280`	`280`	`+`
`281`	`281`	Add your registry's name to the manifest. The following command assumes that your private repository's name is the same as the source repository and adds your private registry's name to the file. Replace [.replaceable]`111122223333.dkr.ecr.region-code.amazonaws.com` with your registry. This line assumes that you named your private repository the same as the source repository. If not, change the `eks/aws-load-balancer-controller` text after your private registry name to your repository name.
`282`	`282`	`+`
`283`	`283`	`[source,shell,subs="verbatim,attributes"]`
`284`	`284`	`----`
`285`		`-sed -i.bak -e 's\|public.ecr.aws/eks/aws-load-balancer-controller\|111122223333.dkr.ecr.region-code.amazonaws.com/eks/aws-load-balancer-controller\|' ./v2_11_0_full.yaml`
	`285`	`+sed -i.bak -e 's\|public.ecr.aws/eks/aws-load-balancer-controller\|111122223333.dkr.ecr.region-code.amazonaws.com/eks/aws-load-balancer-controller\|' ./v2_13_3_full.yaml`
`286`	`286`	`----`
`287`	`287`	`.. (Required only for Fargate or Restricted IMDS)`
`288`	`288`	`+`
`@@ -306,19 +306,19 @@ spec:`
`306`	`306`	`+`
`307`	`307`	`[source,shell,subs="verbatim,attributes"]`
`308`	`308`	`----`
`309`		`-kubectl apply -f v2_11_0_full.yaml`
	`309`	`+kubectl apply -f v2_13_3_full.yaml`
`310`	`310`	`----`
`311`	`311`	. Download the `IngressClass` and `IngressClassParams` manifest to your cluster.
`312`	`312`	`+`
`313`	`313`	`[source,shell,subs="verbatim,attributes"]`
`314`	`314`	`----`
`315`		`-curl -Lo v2_11_0_ingclass.yaml https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.11.0/v2_11_0_ingclass.yaml`
	`315`	`+curl -Lo v2_13_3_ingclass.yaml https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.13.3/v2_13_3_ingclass.yaml`
`316`	`316`	`----`
`317`	`317`	`. Apply the manifest to your cluster.`
`318`	`318`	`+`
`319`	`319`	`[source,shell,subs="verbatim,attributes"]`
`320`	`320`	`----`
`321`		`-kubectl apply -f v2_11_0_ingclass.yaml`
	`321`	`+kubectl apply -f v2_13_3_ingclass.yaml`
`322`	`322`	`----`
`323`	`323`
`324`	`324`
Original file line number	Diff line number	Diff line change
`@@ -87,7 +87,7 @@ To migrate from the ALB Ingress Controller for Kubernetes to the {aws} Load Bala`
`87`	`87`	`+`
`88`	`88`	`[source,shell,subs="verbatim,attributes"]`
`89`	`89`	`----`
`90`		`-curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.11.0/docs/install/iam_policy_v1_to_v2_additional.json`
	`90`	`+curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/install/iam_policy_v1_to_v2_additional.json`
`91`	`91`	`----`
`92`	`92`	. If your cluster is in the {aws} GovCloud (US-East) or {aws} GovCloud (US-West) {aws} Regions, then replace `{arn-aws}` with `arn:aws-us-gov:`.
`93`	`93`	`+`
Original file line number	Diff line number	Diff line change
`@@ -164,7 +164,7 @@ eksctl create fargateprofile \`
`164`	`164`	`+`
`165`	`165`	`[source,bash,subs="verbatim,attributes"]`
`166`	`166`	`----`
`167`		`-kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.11.0/docs/examples/2048/2048_full.yaml`
	`167`	`+kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/examples/2048/2048_full.yaml`
`168`	`168`	`----`
`169`	`169`	`*** Private::`
`170`	`170`
`@@ -173,7 +173,7 @@ kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-bala`
`173`	`173`	`+`
`174`	`174`	`[source,bash,subs="verbatim,attributes"]`
`175`	`175`	`----`
`176`		`-curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.11.0/docs/examples/2048/2048_full.yaml`
	`176`	`+curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/examples/2048/2048_full.yaml`
`177`	`177`	`----`
`178`	`178`	.... Edit the file and find the line that says `alb.ingress.kubernetes.io/scheme: internet-facing`.
`179`	`179`	.... Change [.replaceable]`internet-facing` to `internal` and save the file.
`@@ -189,7 +189,7 @@ kubectl apply -f 2048_full.yaml`
`189`	`189`	`+`
`190`	`190`	`[source,bash,subs="verbatim,attributes"]`
`191`	`191`	`----`
`192`		`-curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.11.0/docs/examples/2048/2048_full.yaml`
	`192`	`+curl -O https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/examples/2048/2048_full.yaml`
`193`	`193`	`----`
`194`	`194`	`... Open the file in an editor and add the following line to the annotations in the ingress spec.`
`195`	`195`	`+`
`@@ -237,7 +237,7 @@ image::images/2048.png[2048 sample application,scaledwidth=100%]`
`237`	`237`	`+`
`238`	`238`	`[source,bash,subs="verbatim,attributes"]`
`239`	`239`	`----`
`240`		`-kubectl delete -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.11.0/docs/examples/2048/2048_full.yaml`
	`240`	`+kubectl delete -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.13.3/docs/examples/2048/2048_full.yaml`
`241`	`241`	`----`
`242`	`242`	`** If you downloaded and edited the manifest, use the following command.`
`243`	`243`	`+`