Комментарии:
awesome content 👌
ОтветитьWell done Sir! 👏
Ответитьvery cool
Brief, useful and practical
thank you so much 🙏👌
THANK YOU THANK YOU THANK YOU
Simple, great, fast, and to the point.
Keep up the great work man!
Straight to the point.
Ответитьcool
ОтветитьAwesome thanks , I am looking forward to understand how the whole istio security stack works and your videos have been very useful
ОтветитьWowwww this is really incredible. No fuss, no lags, no spins.... No blah blah blah ....STRAIGHT ARROW ONTO TARGET.
Crystal clear and this so easy felt like drinking a starbucks coffee..
super man and thank you very much.
Can you Make a vidéo for trusted certificat
ОтветитьAwesome!! thank you for this clear explanation.
Ответитьhii ,The video is great but i am getting version error
ОтветитьWhich version of ingress is this :O
Ответитьwould be great if you could update this: `error: unable to recognize "base-notebook/ingress.yml": no matches for kind "Ingress" in version "extensions/v1beta1"`
ОтветитьGood video! Next, how do we create a Let's Encrypt certificate?
Ответитьthe in depth style is more needed - since this is a tutorial ... = )
ОтветитьAt k8s 1.20 it doesn't work. It is impossible to create Ingress.
ОтветитьThanks for the easy solution - How do we make these keys as trusted tls and use them on internet.
ОтветитьI got nervous when he had the single ">" after he said "append". I don't know how to yell ">>", but I'm pretty sure that I was.
Ответитьso the ingress.yaml still specifies port 80 after switching to tls version?
ОтветитьClear crystal explanation thank you very much
Ответитьhi thanks for posting this video. i tried following and got everything working up to the point where you access the web server thru the browser. I am getting ```uses an invalid security certificate. The certificate is not trusted because it is self-signed. Error code: MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT```. When I curl it using those -k and --cacert flags it works fine, I can see the HTML content. What am I doing wrong?
ОтветитьAnd it works!
ОтветитьThanks for the tutorial. I'm using Docker Desktop default K8S cluser, so what's the equivalent of the cmd : minikube addons enable ingress ?
ОтветитьAmazing, thanks for this tutorial. Great explanation.
Ответитьvery nice explanation and example
Ответитьthe tutorial is very helping full sir especially about the imperative command to generate the certificate very cool thing!!!
ОтветитьNice!
A couple of words. I needed to play again and again because you go too fast, but may be its a very personal appreciation. However, after not having clear what the documentation means in the TLS subject, you helped me. Thanyou!.
The pace of this video was excellent!
ОтветитьYour videos are one of the best explained videos I have seen. Well done. Looking forward to more
ОтветитьAwesome tutorial! Thanks a lot.
ОтветитьGreat explanation. This example shows TLS termination, is it possible to achieve TLS bridging (end to end encryption) with Ingress ?
ОтветитьShort and sweet! Love it.
ОтветитьToo bad the commands you typed aren't available in the description of the video. Other than that it shouldn't be hard to replicate
ОтветитьHi there great video ...if you get some time can you add something on kong api gateway as well ...
ОтветитьVery good video. I have added tls to ingress and all external requests are protected. Could you tell how set up tls for internal k8s connection? For example I have auth service that available outhside and inside of k8s.
ОтветитьThanks a lot for the clear tutorial !
ОтветитьGreat !!!
ОтветитьCool, Great job
Ответитьvery useful for learning.. thanks
ОтветитьCan we generate live ssl certficate and put it in ingress ? Will it work?
Ответитьthis echo "$(minikube ip) ..., do you really do that in your real life?
Ответитьwow that's a loud keyboard! Thanks for the great videos, nice and dense with no fluff, just like I like
ОтветитьThank you man, nice video!
Ответить