Deploying Pods to Fargate
Deploy the sample application
Deploy the game 2048 as a sample application to verify that the AWS Load Balancer Controller creates an Application Load Balancer as a result of the Ingress object.
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/main/docs/examples/2048/2048_full.yaml
You can check if a Deployment has completed
kubectl -n game-2048 rollout status deployment deployment-2048
Next, run the following command to list all the nodes in the EKS cluster and you should see output as follows:
kubectl get nodes
If your cluster has any worker nodes, they will be listed with a name starting wit the ip- prefix.
In addition to the worker nodes, if any, there will now be five additional fargate- nodes listed.
These are merely kubelets from the microVMs in which your sample app pods are running under Fargate, posing as nodes to the EKS Control Plane. This is how the EKS Control Plane stays aware of the Fargate infrastructure under which the pods it orchestrates are running. There will be a “fargate” node added to the cluster for each pod deployed on Fargate.