In this section, we will discuss using ELB with the Amazon Elastic Kubernetes service EKS. So far, ACME has been integrating its ELB with other AWS services in order to provide access to its website hosted on EC2 Instances. In the future, ACME intends to containerize its application and host those containers on the Amazon Elastic Kubernetes Service EKS. When working with EKS, ACME will still need to load balance traffic to their containers hosting their website application. 

To do this, they will need to integrate an elastic load balancer with their EKS clusters. Historically, when deploying an EKS cluster and using a YAML file to deploy a service, a classic load balance was being created for you. This should be avoided today. Although classic load balancers are still supported, it is recommended that you use either an Application Load Balancer or a Network Load Balancer with your EKS cluster. To integrate ELB with EKS, you can create an Ingress controller or define a load balancer type in a service YAML file. If you create an Ingress controller, you're defining an Application Load Balancer. If you define a load balancer type in a service YAML, you're defining a Network Load Balancer. 

The following YAML code will be used as part of the configuration of your EKS cluster to create an Ingress controller, deploying an Application Load Balancer. The following YAML will be used as part of your EKS service definition to deploy a load balancer type, deploying a network load balancer as part of your Kubernetes service. For more information on EKS management and deployment, see the following learning path. Once the load balancer is defined, you will see it in your list of load balancers in the AWS console and can then integrate the load balancer with other AWS services in the way is discussed in this course. For example, you can use route 53 to map your friendly name to the load balancer name using an alias record.