This video demonstrates how to load balance your application on EKS using Kubernetes ingress. Git hub: github.com/listentolearn/aws-... Deploying a sample application on EKS: • Elastic Kubernetes Ser...
Hi Anubhav, thanks :) Node port service is used to expose the service running in each node at a static port. Then load balancer balances the traffic between the node and exposes the traffic externally.
it is good overview with practical, Thank you. One query i have is what if i have multiple services in my cluster? if i update the ingress file and re-run will it create a new load balancer or will it just update the paths to existing load balancer ?
Hi Sai, Changing the underlying services within the ingress will not recreate the entire load balancer. It will update/recreate the target groups and listeners associated with the load balancer.
Quick update the load balancer policy is not working, I had to update the same to create the Load Balancer, otherwise the host address was coming as blank.
we are creating service account in kube-system namespace. Deployment & Ingress are getting created in game-2048 namespace. Then isn't that an issue? Because I heard every namespace will get default service account, so in that case how game-2048 can use our aws service account?
Hi Sathish, The service account created under kube-system namespace is attached to the load balancer controller role and allows permissions related to load balancing. So, this is a generic and be used across the cluster. That is the reason its tied to kube-system namespace. While the ingress is specific to our use case. So, its tied to game-2048. Hope that makes sense.
I have this error in ingress: Failed build model due to WebIdentityErr: failed to retrieve credentials caused by: InvalidIdentityToken: Incorrect token audience status code: 400 Please advise.
Hi sangnd, Its hard to tell without looking at the logs. You can try running the below command from cmd to check whats going on. kubectl logs -f -n kube-system -l app.kubernetes.io/instance=aws-load-balancer-controller Also, ensure that you have the correct tags set for the subnets.
This videos explains the cluster setup and base infra that I used for this ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-I6yqVBhNXxY.html. I am using just one default security group, so I dint have to do anything additional. If you're using multiple security groups attached to worker node, exactly one security group must be tagged as follows. Replace my-cluster with your cluster name. Key - kubernetes.io/cluster/my-cluster Value - shared or owned
Hi I have created the load balancer controller and the ingress as mentioned. But the ALB is not getting created and not getting the address for the ingress. When checked the logs below message appear continuously - 1 leaderelection.go:248] attempting to acquire leader lease kube-system/aws-load-balancer-controller-leader
Hi! Nice guide, but I met this problem: kubectl logs -n kube-system aws-load-balancer-controller-66f9fb7dc5-gchsh {"level":"info","ts":"2024-03-05T15:01:09Z","msg":"version","GitVersion":"v2.7.1","GitCommit":"f689bbdf73d30f23b44acfef2c3b8e7280cd66ee","BuildDate":"2024-02-09T16:21:17+0000"} {"level":"error","ts":"2024-03-05T15:01:13Z","logger":"setup","msg":"unable to initialize AWS cloud","error":"failed to introspect vpcID from EC2Metadata or Node name, specify --aws-vpc-id instead if EC2Metadata is unavailable: failed to fetch VPC ID from instance metadata: EC2MetadataError: failed to make EC2Metadata request \tstatus code: 401, request id: "}
