The AWS ELB add-on configures the AWS Load Balancer Controller for use by the cluster.
This add-on is required for routing external traffic to the cluster with:
The awsELB addon has one optional parameter of elbRole. If provided, the controller will this role to access the AWS API. If no role is provided then the recommended role from AWS will be used. The AWS Workload Identity Add-On is leveraged in the configuraiton of the load balancer controller to configure access for this role.
Enable AWS ELB w/ a custom role
Enable AWS ELB w/ the built-in role
This add-on can be enabled at cluster creation or afterwards.
Kubernetes
in the left sidebar, and click on the cluster you wish to configure.Add-ons
, find the AWS ELB
add-on in the list, and toggle it on.The AWS Load Balancer Controller needs to know which subnets it is allowed to use for internet facing and internal load balancer resources for this cluster.
The following tags must be added to AWS Subnets in order to designate how they can be used:
Private subnet tag:
Key: “kubernetes.io/role/internal-elb” Value: “1”
Public subnet tag:
Key: “kubernetes.io/role/elb” Value: “1”
After enabling the AWS ELB add-on, check to make sure that the controller is running and that it can access the AWS API using AWS Workload Identity. Connect to the MK8s Cluster using the Kubernetes Dashboard or the kubectl CLI.
kube-system
namespace from the drop down menu on the top of the page.Pods
on the left menu.Logs
.A live log view will open. Inspect the output for any error messages.
If the controller cannot access the AWS API, verify that you have performed Step 1 for the AWS Identity Add-On.
Aditional troubleshooting steps are available in this AWS Knowledge Center article.
Create the following Service
and Deployment
in your Managed Kubernetes cluster.
This example demonstrates creating a workload that is exposed externally.
Once the objects are created, check the status of the Service. An Endpoint should be created for it automatically and listed under the External-IP column of the output.
Check the describe output of the service and the logs of the load balancer controller if the endpoint is not created or it is not working correctly.
The AWS ELB add-on configures the AWS Load Balancer Controller for use by the cluster.
This add-on is required for routing external traffic to the cluster with:
The awsELB addon has one optional parameter of elbRole. If provided, the controller will this role to access the AWS API. If no role is provided then the recommended role from AWS will be used. The AWS Workload Identity Add-On is leveraged in the configuraiton of the load balancer controller to configure access for this role.
Enable AWS ELB w/ a custom role
Enable AWS ELB w/ the built-in role
This add-on can be enabled at cluster creation or afterwards.
Kubernetes
in the left sidebar, and click on the cluster you wish to configure.Add-ons
, find the AWS ELB
add-on in the list, and toggle it on.The AWS Load Balancer Controller needs to know which subnets it is allowed to use for internet facing and internal load balancer resources for this cluster.
The following tags must be added to AWS Subnets in order to designate how they can be used:
Private subnet tag:
Key: “kubernetes.io/role/internal-elb” Value: “1”
Public subnet tag:
Key: “kubernetes.io/role/elb” Value: “1”
After enabling the AWS ELB add-on, check to make sure that the controller is running and that it can access the AWS API using AWS Workload Identity. Connect to the MK8s Cluster using the Kubernetes Dashboard or the kubectl CLI.
kube-system
namespace from the drop down menu on the top of the page.Pods
on the left menu.Logs
.A live log view will open. Inspect the output for any error messages.
If the controller cannot access the AWS API, verify that you have performed Step 1 for the AWS Identity Add-On.
Aditional troubleshooting steps are available in this AWS Knowledge Center article.
Create the following Service
and Deployment
in your Managed Kubernetes cluster.
This example demonstrates creating a workload that is exposed externally.
Once the objects are created, check the status of the Service. An Endpoint should be created for it automatically and listed under the External-IP column of the output.
Check the describe output of the service and the logs of the load balancer controller if the endpoint is not created or it is not working correctly.