Securing Kubernetes Ingress With Let’s Encrypt

Securing Kubernetes Ingress With Let’s Encrypt

DigitalOcean

2 года назад

16,651 Просмотров

Ссылки и html тэги не поддерживаются


Комментарии:

@Ecolariat
@Ecolariat - 28.11.2023 00:42

Great Video! Thank you - got everything up and running. One question - how do you remove the comments in code . ? I've been manually deleting, what shortcut keys did you use in the video to remove them?

Ответить
@sergiovelazquez958
@sergiovelazquez958 - 05.08.2023 05:46

Excellent video. It was very helpfully. Congratulations

Ответить
@user-sm1sd6uw5o
@user-sm1sd6uw5o - 15.06.2023 14:37

Thank you so much for this video. It's very helpful.

Ответить
@anishsinha1708
@anishsinha1708 - 19.04.2023 23:35

From the bottom of my heart, thank you so much Kim and DigitalOcean. This tutorial is so unbelievably high quality and really helped me set up K8S for my company.

Ответить
@alfredorivera7038
@alfredorivera7038 - 30.03.2023 18:16

finally my ingress works!! thank you

Ответить
@Boriu
@Boriu - 17.03.2023 20:00

Thank you so much Kim for this wonderfull lesson!!

Ответить
@ignacio6655
@ignacio6655 - 12.01.2023 19:16

This was an excellent tutorial, many thanks. I would like to ask something, in the ingress.yaml you set the port number to 8080, when actually the service runs on port 80. It was fixed in the GitHub repo as well. My question is: why did it work if the service was only listening to port 80? I have tried both ports 80 and 8080 and work. I cannot find an explanation for this, maybe because port 80 and 8080 are treated by k8s as the same port? Thanks!

Ответить
@kk3528
@kk3528 - 16.12.2022 02:00

Please do not waste time in unnecessary talk just please get straight to your topic of your video .thanks

Ответить
@jdogstersc
@jdogstersc - 09.10.2022 05:26

Kim you are amazing. Thank you so much for the help!!

Ответить
@anonanon3066
@anonanon3066 - 17.09.2022 22:40

Many fucking thanks to you! Now my readers can be absolutely certain that it's my brainfarts they're reading.

Ответить
@udaykiran5834
@udaykiran5834 - 25.08.2022 22:33

I reconfigured the ingress but still the certificate is not getting generated.

[ec2-user@ip-172-31-15-131 ~]$ kubectl -n backend get issuer
NAME READY AGE
letsencrypt-nginx True 13m
[ec2-user@ip-172-31-15-131 ~]$ kubectl -n backend get order
No resources found in backend namespace.
[ec2-user@ip-172-31-15-131 ~]$ kubectl -n backend get challenges
No resources found in backend namespace.
[ec2-user@ip-172-31-15-131 ~]$ kubectl -n backend get certificaterequests
No resources found in backend namespace.
[ec2-user@ip-172-31-15-131 ~]$ kubectl -n backend get certificate
No resources found in backend namespace.

Ответить
@master2466
@master2466 - 20.08.2022 17:36

This is how the demo should be. She explains everything in clear details, no show off or cryptic talk like some or hiding the real details. She is clearly enjoying the talk and not worried about anything. Well done. Can't parise enough

Ответить
@drglz
@drglz - 03.05.2022 18:13

This video made clear how ingress and cert-manager work that's been baffling me for quite a while. Thank you!

Ответить
@unknownhero6187
@unknownhero6187 - 20.03.2022 15:40

How does actually a Digital Ocean Load Balancer implemented? Is it Nginx or Istio? Is it l4 or l7 load balancer?

Ответить
@unknownhero6187
@unknownhero6187 - 19.03.2022 23:22

Thank you for the excellent tutorial!
Could you please explain why we need a Digital Ocean Load Balancer in front of our k8s cluster? Can't the Nginx ingress controller handle it on its own?

Ответить