@AntonPutra
To tear down cluster, first run "terraform destroy --target helm_release.external_nginx" then "terraform destroy"
@dma9511
Thanks for your lessons! very useful! And thank you for the updates, your examples help me to create my first prod-ready eks cluster with Terraform! Have a great day!
@kevinvoyer6697
I really appreciate the quelity of this content, thank you :)
@ĐạtTruong-m2y
Could you give me video link that you said on 2:41 about content "private ingress with private dns and client vpn".
@DevOpsGang
Great video Sir, one very important question, will WAF work with nginx ingress controller (network load balancer layer 4)? same traefik do provision layer 4 network load balancer, how WAF will work? of Cloud Armor?
@csmithDevCove
its official - i hit the bell icon. Well done @AntonPutra.
@ganges6661
I’m so grateful to you. ⭐️
@ZergStylexDD
Great lesson, as always. Keep it going!
@greggles_b
Thanks Anton, maybe I missed in the video, but at the end of the last video you said which of ALB Ingress vs Nginx Ingress you would recommend? The highlights of Nginx: - Acts as a central proxy for all services in k8s, so you can monitor all your traffic to the cluster (sounds like the limitation with ALB is you'd get multiple ALBs per Ingress, unless you use an Ingress Group which has some caveats, so not as easy to monitor) - Supports custom TCP and UDP services (in AWS LB, you'd get one NLB per LB-service) Main cons: - More work to set up SSL termination especially with DNS-01 challenge - If you want to use IP mode, you'd need to also install the AWS LB controller anyway for the NLB(?) The highlights of ALB ingress: - Routes traffic direct from ALB to pod IPs, avoiding the additional nginx proxy, so maybe a bit cheaper, less to debug, and marginally lower latency? - Seems easier to secure with SSL certs - Only requires a single controller Main cons: - Each LB-service creates a new NLB. (could you not just use ClusterIP for all services to avoid any NLBs?) Not so clear which one is the better approach. Cheers!
@codeklaudia9696
This video is a relief to me. Ive been looking for a tutorial on this for a long timme. Thank you. Do you think you could make a similar one through the AWS console ?
@arunreddy1436
nginx ingress controller is one of the alternatives for the aws load balancer controller , then why do we need to install aws load balancer also before installing nginx controller ? got confused.. could you please explain insights here
@prashlovessamosa
Thanks Anton
@hgn213
Thank you so much. Thank you thank you thank you
@prateeksarangi9187
Thanks @anton for such lovely video, great content, waiting for your video on client VPN to secure the traffic so that corporate team member can able to only access that using the Private DNS
@GabrielPozo
Thank you!!!
@10x57hg
Very good playlist. Could you please add the internal nginx part for the private dashboards ? Thank you!
@Krishreddy-u2k
Thanks for sharing one more awesome lesson, any plans to make a video on using AWS private certificate authority (ACM) with aws-pca-issuer add-on ? thanks
@YellowMom08
why can't I access the NLB's DNS without cert in a browser when I am using ingress as per the tutorial. but earlier when I was using service of type "LoadBalancer" I was able to access my app through the browser using only the dns of NLB from aws console?
@santirodriguez588
Could you explain how we can configure traefik instead nginx?
@AntonPutra