Take a look at external-dns. It watches for ingress hostnames and automatically creates DNS records. GoDaddy is also supported - github.com/kubernetes-sigs/external-dns
you have 2 options. 1. just use annotation on the ingress and "Certificate" will be created automatically. 2. Instead of annotation you can manually create "Certificate" which will generate private key and obtain public cert from letsencrypt. first option is prefered but it's up to you
Very good video, but if I have k8s on premises behind firewall and not using AWS Route53 DNS service? I use other that not in CertManager provider list. What about this case?
@@tdslot No, you can’t use public CA to issue certificates for your private domains, unless of course you own public domain as well. But in that case you would face dns double horizon issues. If you only need to protect your internal domains, you need to use self sign ca.
🔴 - To support my channel, I’d like to offer Mentorship/On-the-Job Support/Consulting - me@antonputra.com
Love how you explain everything so clearly! I've never known how the challenges exactly worked when integrating them with traffic foe another project.
thank you!
Pure gold! Thank you, Anton. Keep going.
than you!
This is best !! Please keep teaching!!
Thanks so much for this tutorial. Keep going!!
welcome!
Спасибо. Привет из Флориды
bez problem :)
Your content is helping me a lot, thank you very much
Welcome! This one is more niche-specific, but I think a lot of people using Nginx Ingress will find it useful.
Hi @AntonPutra, how do I get access to the files/resources. I have just subscribed to your videos
@@richinex I have a link under each video - github.com/antonputra/tutorials/tree/main/lessons/194
@@AntonPutra True I found it. Thanks
Can you throw some more light on openid connect provider?
Can I use same with GoDaddy DNS?
Take a look at external-dns. It watches for ingress hostnames and automatically creates DNS records. GoDaddy is also supported - github.com/kubernetes-sigs/external-dns
Will it work if we provide temp domain by editing /etc/hosts in local cluster??
Amazing stuff , which tool do you use to create those extraordinary diagrams ?
thanks! i use adobe suite
@@AntonPutra thanx a lot for the quality 🙏🏻🙏🏻🙏🏻. Do have any plan to create some paid courses on udemy or on your own platform ?
@@soufiane22v thanks, maybe in the future
Awesome, Thanks, the best
welcome!
Thanks! Do I need to create kind Certificate when already install helm cert-manager?
you have 2 options. 1. just use annotation on the ingress and "Certificate" will be created automatically. 2. Instead of annotation you can manually create "Certificate" which will generate private key and obtain public cert from letsencrypt.
first option is prefered but it's up to you
There is a way to use a certificate from AWS Certificate Manager in terraform with auto update for k8s ?
Yes, you can. I had an example somewhere in my repo, but I don't remember where.
Very good video, but if I have k8s on premises behind firewall and not using AWS Route53 DNS service? I use other that not in CertManager provider list. What about this case?
Thanks!. Just use cert-manager with http-01, it only requires you to open port 80 and no additional integrations.
@@AntonPutra Hello, if I understood correctly then my all internal host names that exist on ingress will be exposed to public internet?
@@tdslot No, you can’t use public CA to issue certificates for your private domains, unless of course you own public domain as well. But in that case you would face dns double horizon issues. If you only need to protect your internal domains, you need to use self sign ca.
Thank you so much @anton, amazing stuff and how you explain it 😮😮…
It’s possible to get you .bashrc custom configuration :-)) thanks
thanks, well it's zshell - ohmyz.sh/
@@AntonPutra thank you ;-))