1:43 I love how you used that opportunity to flash those biceps 🤣🤣🤣
@abhishekpadadale
4 жыл бұрын
Thank you for explaining kube proxy !!! Your explanation is Simple yet very effective and easy to grasp
@Achillerostand
3 жыл бұрын
Hello, thank you for your explanations. I really appreciate the "Behind the scene" part. Could you please make a full "behind the scene" video(s) explaining the most important linux feature concepts used by Docker/Kubernetes? Best regards
@patricknelson
2 жыл бұрын
I actually usually just standardized on port 8080 instead. Still easy to remember but has the advantage of not requiring the container user itself to run with special privileges (helps a bit with security).
@pallavkanaujiya
4 жыл бұрын
this is the best explanation i have came across!! Bloody brilliant!!
@OggerFN
3 жыл бұрын
*I have come across the 'have' is already past tense
@Tech-ub8dd
7 ай бұрын
Thank you for demystifying the k8s services behind the scenes, it was clear and simple explanation! Subbed and looking forward to explore more of your videos where it breaks down the 'magic' behind the scenes
@ravinathedirisinghe4024
2 жыл бұрын
This is 2021 and still a valuable video
@timurjoro1995
2 жыл бұрын
You made it look so easy. I think my 4-year old daughter would understand this :)
@zmxn007
Жыл бұрын
Thanks for the very clear explanation
@umermustafa2560
4 жыл бұрын
I cant thank you enough for all your videos👍
@randulakoralage5743
2 жыл бұрын
such a clear explanation! good job
@ashwaniahuja
3 жыл бұрын
super video to explain the concepts , I love your all other tutorials/demos as well.
@wanderless3863
2 жыл бұрын
very well explained. it really helped.
@hariomgarg1127
2 жыл бұрын
Thank you sir, I really appreciate. nice explation and easy to learn.
@djstr0b3
4 жыл бұрын
Excellent video. Thanks heaps for the deep dive
@stefanw8203
3 жыл бұрын
Great, - really great. This was an awesome explanation!
@kevinyu9934
3 жыл бұрын
Very clear. Awesome content!
@abhilashpatel6852
8 ай бұрын
this playlist just made it to my list. I will follow it up one by one. main reason being you are using vscode.
@paradoxfx
4 жыл бұрын
Thank you. Very detailed and clear.
@vishekkumar3184
2 жыл бұрын
Great explanation thanks :)
@alxx736
2 жыл бұрын
What is the difference between service discovery in Kubernetes and Service Discovery in Istio?
@massgo969
4 жыл бұрын
Yeah !:), Great explanation thank you, Please add more and more real time stuff on based microservices.
@wolfdhib1
3 жыл бұрын
great explanation but I think you have missed NodePort services.
@MohammadMoynulHaqueBiswas
3 жыл бұрын
Great video
@MZ-ii4bb
3 жыл бұрын
Thank you
@Itsme-kx1us
Жыл бұрын
Tq sir
@PePTo-dx2yj
4 ай бұрын
sorry my question my english bad)) but how Service choose POD (in replicaset for example have 5 POD) where network traffic must go, which mechanizm use for it? ty
@MarcelDempers
4 ай бұрын
Service has a "selector" which selects the pods by label. Kubernetes will then define endpoints (local IP) for each pod that is "selected". When you `kubectl describe` a service you will see endpoints under it. The endpoints are what ends up being load balanced
@PePTo-dx2yj
4 ай бұрын
@@MarcelDempers ty , sorry may be Im not good explain, I mean between endpoints which use roundrobin or somethink else?
@wayne1435
4 жыл бұрын
Nice one
@harilakshminarayanaa9469
2 жыл бұрын
Who is listening this in 2022
@brianhorakh1104
3 жыл бұрын
this could have been as an interactive cli-demo using _b00t_
@mitch5222
2 жыл бұрын
Is there option like in docker swarm ( mode: host )?
@herousall9353
4 жыл бұрын
Bien fait
@SunnyG1987
4 жыл бұрын
Awesome
@squalazzo
3 жыл бұрын
a clarification: labels in deployment spec are used to match labels in containers, while labels in deployment metadata are used to be selected by the service, right? Even if they're named the same, labels in deployment metadata and in its spec section are NOT related, or am i wrong? Thanks
@mgjulesdev
Жыл бұрын
I know this is 1 year old. A deployment manages a replicaSet which in turn manages a pod. The service has a selector to know which pods to target and not the deployment or replicaSet. Same the replicaSet has a selector to know which pods to manage.
@squalazzo
Жыл бұрын
@@mgjulesdev yeah, i know now, i got both cka and ckad in the meantime :D
@zaibakhanum203
2 жыл бұрын
Iam not able to access my application using loadbalancer service type can u please help
@ajadavis2000
2 жыл бұрын
would u want to use port 80 across the whole org or would 443 be better for more secure?
@MarcelDempers
2 жыл бұрын
Generally offload SSL at the edge, so 443 for ingress controllers (public traffic), and private connections all over 80 (all pods) is a more common approach. So 80 across all internal private comms.
@ajadavis2000
2 жыл бұрын
@@MarcelDempers thank u , ok i understand, so for the port mirroring notated in the service.yaml @8:40 the pod is reachable via network call internally on port 80 for its respective internal subnet, and port 5000 is the localhost port of the pod?
@MarcelDempers
2 жыл бұрын
100% The pod should also have an IP and can be reached on port 5000 if you know the IP, but service is the best approach since its a DNS so you dont worry about changing pod IPs
@ajadavis2000
2 жыл бұрын
@@MarcelDempers hm i thought we were reaching pods on port 80 using the pod IP - I thought the 5000 port would be only specific to the pod itself in its own specific namespace
@laurentiuspurba2735
3 жыл бұрын
What if a POD in cluster A wants to talk to a Service-1 in cluster B?
@MarcelDempers
3 жыл бұрын
You would have to either 1) expose Service-1 in cluster B using service type=LoadBalancer or 2) Expose Service-1 using an ingress (Recommended)
@prashantjha439
4 жыл бұрын
can single worker node run pods with different labels or it is not recommended or k8 controller manager can schedule a pod in any worker node irrespective of label
@MarcelDempers
4 жыл бұрын
A single node can run multiple pods or you can pin pods to a single node with node selectors. However its best avoided since a node outage will sink all the pods on that node. Also best to decouple your application from the node. Best to schedule on any node unless you have pods that have state on certain nodes, like a data store. In that case you want to pin pods to the node that has it's data and use a StatefulSet. Managing stateful workloads also depends on how well the software in the pod can react to restarts. Databases like Cockroach DB is good at dealing with this.
@prashantjha439
4 жыл бұрын
@@MarcelDempers , Thanks Marcel Can you also please upload a video where you also touch upon envoy proxy and istio and how it runs alongside k8 pods as sidecars for communicating and how istio/service mesh helps in service discovery. i know these concepts in broad level , but learning these same things from you would be great , given your expertise and way of explaining things
@johnlam900
4 жыл бұрын
Came for the memes, accidentally learnt shit.
@shannonchoy1449
4 жыл бұрын
The services refer specially to REST services or can they be of any kind of protocol? Since K8 does the load balancing for us automatically does that mean we no longer need to include load-balancers for our systems? Thank you for the video!
@shannonchoy1449
4 жыл бұрын
I just realized I did not see your video on Ingress for Beginners.
@MarcelDempers
4 жыл бұрын
You most likely dont need other proxies internally just to do basic load balancing. For REST services you will want an Ingress controller at your edge which can serve multiple services to the public. Be sure to checkout the most recent Ingress video too. (I have 2 now): kzitem.info/news/bejne/1m9qnneLi351fXY
@TythosEternal
Жыл бұрын
Dear God this explained so much "behind the scenes" it's almost depressing
@trash2trash
Жыл бұрын
NOTHING about Load Balancing. Only one comment and thats all.
@coneryj
2 жыл бұрын
please talk slower and take a breath between sentences
Пікірлер: 57