🔴 - To support my channel, I’d like to offer Mentorship/On-the-Job Support/Consulting - me@antonputra.com 👉 [UPDATED] AWS EKS Kubernetes Tutorial [NEW]: ru-vid.com/group/PLiMWaCMwGJXnKY6XmeifEpjIfkWRo9v2l&si=wc6LIC5V2tD-Tzwl
Great tutorial! Can we have video on managing multiple ingress controller in the same cluster and how to define which ingress controller a ingress resource will use to route traffic? - confused with Ingress Class
simply spread them between different namespaces and make sure they have different ingress class names. If you use helm, just update default ingress class to something
Hi...I've tried the ingress rule as path based routing rather than hostname based, while checking in the grafana, I've seen only the ingress of hostname based routing, I couldn't see the path based ingress file metrics...Can you give the idea about this...? I need to see path based routing metrics also...
Great video but i confused does values.yml consist of both nginx class and kubernetes controller class together? could you explain? should i know all object of nginx and kubernetes class?
Yes it does, it's done for legacy compatibility. For example cert-manager aims to support as many ingresses as posible to do that they decided to use old "annotations" instead of ingress classes. Nginx ingress class supports both class name and old annotation "nginx class"
Hey Aton, you explaination is too good. But i have a doubt. what annotation should we use if install ngnix ingress controller on kubernetes cluster which is on our own Bare metal servers.
it depends on the version of controller and k8s cluster. Most likely you would also need to use ingress class. Annotations mostly used by custom controllers that you deployed to k8s, I would recommend to search what annotations your controller support
I followed the same steps but on Nginx Ingress TCP Example part I can't connect to postgres. The only different thing I did is used external Ip of Loadbalancer instead of creating CNAME, but does it make any difference ?
I am in a weird situation, I follow your examples to create the EKS cluster using terraform but for the ingress controller we need to do the irsa thing, right? i.e. setting the service account with the IAM roles and the identity provider in AWS part. I am not able to fix that and it is not present in your tutorials. When I create the ingress controller and the ingress, everything is fine just the ingress controller is not able to create the alb for that ingress. Could you please help me here?
I have a new tutorial with explanation how to set up irsa. antonputra.com/Terraform/how-to-create-eks-cluster-using-terraform/#create-iam-oidc-provider-eks-using-terraform
Thank you for the great content. I have question, I want to use Amazon Certificate Management (ACM) certificate for TLS/SSL in Nginx Ingress, How can I use it?
You can manually create "tls" type kubernetes secret and point to it in your ingress object. In this case you need to monitor yourself certificate expiration.
I'm getting this error "Error syncing load balancer: failed to ensure load balancer: LoadBalancerIP cannot be specified for AWS ELB" when setting LoadbalancerIP for controller service, Any idea
Hello I'm using the terraform for the infrastructure provisioning but I cant able to find how can I setup using terraform is there is any way to setup this using terraform as you are using the eksctl tool soo I need to work with eksctl tool with terraform ?
Thx for wonderful session. Can we configure nginx ingress using selected ip from subnet as we do in aks as internal LB ip . I tried in eks it created but with random ip from subnet schema as internal but I want specific ip .
You can allocate an Elastic IP address and use it for your load balancer. aws.amazon.com/premiumsupport/knowledge-center/elb-attach-elastic-ip-to-public-nlb/
@@AntonPutra what u recommend? How to share lb to some namespaces. We have a lot of namespaces and now in default namespace about 100 external services….
@@fil1806 oh, it's pretty standard, you need a single LB for ingress, then you can create ingresses in all your namespaces. They will share the single load balancer.