Комментарии:
amazing explanation.... loved it.
ОтветитьAfter the latest update ingress prime always crashes.... So i can Not play.... the funny thing os that says " fixed crashing "
ОтветитьToo cool
Ответитьif hands on lab please tell me
ОтветитьExcellent!
ОтветитьSorry for 2 years late, but i have question. Between ingress and pod, is it necessary to have load balancer to handle pod?
ОтветитьMore than the explanation Im always fascinated by how these people write in reverse
ОтветитьThis is a good short video on Ingress and service but once you need to make one correction on ip addresses. 169 range IP address in not public address. It is reserved range.
ОтветитьExcellent! GReat explanation and I congratule you for writing in a mirror way :D, that's hard!
Ответитьcommenting so that I get recommended more of ibm contents !
ОтветитьNo better way to explain Ingress. 👍
ОтветитьYou're awesome!
Ответитьhow many ingress can be created for a cluster?
Ответитьcool
ОтветитьGreat explanation
Ответитьamazing work, i like the alert before the interesting parts..
ОтветитьThis is just what I need. Amazing work!
ОтветитьFantastic!
ОтветитьBest 5 minutes video ever for Ingress
ОтветитьMost production environment use cases are to use a load balancer and Ingress in combination! Is it better to load balancer-> ingress or ingress-> load balancer? I think ibm have more scenes! ibm answer is authoritative! How cloud-native components such as Ingress Istio combine them in a production environment and use them in practice! How to design the specific architecture?So ask you guys
Ответитьultimate explanation in short time.. gr8 work
ОтветитьAs you said that we can do routing in ingress; so is that ok to remove the nginx routing logic and implement in ingress ??
ОтветитьVery cool! in 5 minutes you are able to explain that better then a lot of time of anyone else :)
ОтветитьDid you forget to explain a pair of ingress components, ingress controller and ingress itself?
Ответитьgreat video, may I ask what applications did you use to create this video. the writing part with marker is amazing
Ответитьwell done
Ответитьhow these pens are working is there a glass or it's some kind of computer trick
ОтветитьI can't write that neat forwards
ОтветитьA service is a collection of pods that are loads balanced
ОтветитьI love these clips with transparent board. great content
ОтветитьThanks for the great explanation on Ingress. Got a little better understanding on it.
ОтветитьDid you really write from right to left????
ОтветитьWhen you are on a cloud provider, the load balancer will be automatically provisioned for you, but if you are on bare-metal, you should do that yourself manually.
ОтветитьI've watched 5 other full courses and none of them explained Ingress and Nodeports as clearly as you did.
I finally get it! Thank You!
How do I support you or buy your full course?
Very nice!
ОтветитьYour all videos are great!
ОтветитьNice video, thank you for share, I have a question, I recently heard at a conference that it was a good practice to use multiple ingress controllers in Kubernetes. Why?
ОтветитьI don't understand how can all of the instructor can right backwards?
Is it a job requirement for getting into IBM of you guys are simply flipping the video horizontally?
Thank you.
ОтветитьThanks for the video :)
ОтветитьReally well explained, thumbs up !
ОтветитьPremium content 👍
Ответитьi have a service with 10 replicas of a pod exposed by a service on k8s cluster. I want to 4 replicas to serve public APIs (lets say they have /public prefix) and the other 6 replicas to server private(internal) APIs (let's say they don't have /public prefix). I don't think ingress with help here. Is there any other way, this can be achieved?
Ответитьreally clean nice explanation
ОтветитьSo if I understand correctly. The ingress lives on the API server? Or is that another device? Where does the public IP live? I'm assuming again on the API controller or API server.
ОтветитьDo you actually write mirrored or is there some magic behind this? :D hats off and thanks for the great explanation!
Ответитьshort and very well explain. well done IBM team
Ответить