Kubernetes Là Gì? Vai Trò Và Các Thuật Ngữ Phổ Biến
Kubernetes (viết tắt là k8s) góp quý khách rất có thể quản lí lý (hoặc “điều phối”) vớ cả những khối lượng công việc được chứa trong container của bạn, bao gồm cung cấp, connect mạng, cân nặng bằng vận chuyển, bảo mật và mở rộng quy mô. Docker rất có thể chạy song lập mà không cần thiết có Kubernetes, nhưng Kubernetes ko thể sinh hoạt mà ko có cty container như Docker. Kubernetes góp chúng ta loại quăng quật cực kỳ nhiều các quy trình tay chân liên quan tiền đến việc khai triển và mở rộng lớn những containerized applications.
Tiêu đề video: Kubernetes Ingress in 5 mins
Độ dài: 00:05:41, Ngày đăng: 2020-12-19 01:27:38
Tác giả: IBM Technology
Link gốc: https://www.youtube.com/watch?v=NPFbYpb0I7w
Xem video Giới thiệu Kubernetes Giải thích → Tìm hiểu thêm về Kubernetes → Tìm hiểu thêm về Kubernetes Ingress → Tìm hiểu thêm về Cân bằng tải → Đọc blog Kubernetes Ingress → Kiểm tra Dịch vụ IBM Cloud Kubernetes → ► Kiếm huy hiệu với phòng thí nghiệm Kubernetes tương tác MIỄN PHÍ → Có một số cách để hiển thị các ứng dụng của bạn được triển khai trong Kubernetes, nhưng làm thế nào để bạn biết tùy chọn nào phù hợp nhất với mình? Trong video lightboard này, Sai Vennam với IBM Cloud, phân tích trực quan bốn tùy chọn chính (ClusterIP, NodePort, LoadBalancer và Ingress) rất chi tiết và tại sao sử dụng Kubernetes Ingress là lựa chọn tốt nhất để sử dụng trong môi trường sản xuất. Dấu thời gian 0:00 – Intro 0:50 – ClusterIP 1:10 – NodePort 2:44 – LoadBalancer 3:43 – Ingress 5:10 – Lợi ích của Kubernetes Ingress Bắt đầu miễn phí trên IBM Cloud → Đăng ký để xem thêm video tương tự trong tương lai → Kubernetes KubernetesIngress LoadBalancer.
Container Deployment
Container rất dễ để chạy, các quý khách dev hoàn toàn có thể dùng container nhằm tạo nên ra môi trường nhằm dev hoàn hảo trong vài giây, tuy nhiên lúc dùng container ở môi ngôi trường production thì ko đơn giản như vậy. Điều đó ko có tức là bạn dạng thân các container không hữu ích. Các container đã phát triển thành trọng tâm chính của không ít doanh nghiệp muốn tiền phong vào gửi đổi số và có vận tốc ra mắt công ty mới thời gian nhanh chóng.
Các bạn đang theo dõi chuyên mục công nghệ
Web site: https://sapovietnam.com
Nội dung được tổng hợp từ internet. Vui lòng để lại comment nếu muốn đóng góp/ý kiến về nội dung bài post.
Thanks for the video 🙂
Really well explained, thumbs up !
In kuberentes how to do traffic splitting between pods behind a single services, so that each pod can receive equal request/second.
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? 😀 hats off and thanks for the great explanation!
short and very well explain. well done IBM team
Oh. I would love to watch your personal channel, hard to find videos exactly from you, but they are the best.
Sai Venom .. what a badass name !!!
Just a suggestion to not whiteboard at the very bottom of the frame, it ends up overlapping with the subtitles (if enabled)
Only 5 mins and so much content… hats off
The best explanation, I have seen many videos, but this the gem of all
Very nice format thanks!
greatly explain in 5 mini.. to my knowledge/experience NLB is Network Load Balancer right ? correct me if I am wrong !!
Well done bro !
Thanks for the quick video and explanation. On point.
You are writing in mirror or you write normal? Sorry had to ask
Great video. Just one confusion I have. Do we need a load-balancer like Ngnix when using Ingress or Ingress itself act as a load balancer
I have a question, so essentially an Ingress is a Kubernetes component which is not in the form of actual process running as part of cluster itself, but instead ingress makes sures that it maintains the front end and backend configuration needed for an external load balancer process to pick it up and execute outside the cluster?
Thank you for the helpful summary
Excellent explanation!
Very nice explanation, very visual and to the point
Nicely explained. Simple and efficient.
One question i have about ingress: can you build it so that it routes traffic say like 70% on one service and 30% on another when you've got same pods created in each service? I don't know if i was clear enough (:
Great content, amazing explanation 👍
It took me 2 and half mins, watched it in 2x 🙂
psy venom
Nice, good one Sai
very well done, thx!
Basically, Ingress is like Zuul in Spring Cloud
Ambassador next , plz
Excellent video about Kubernetes once again!!
Hi, can anyone teach me how to scale the pods of a single deployment across nodes, or say, group pods from different nodes as a service? I have thought that you can only group pods with labels within a node? I have also thought that you can only scale out pods for a deployment within a node. Is it possible to control that?
so amazing… the way you explain was awesome.. thanks
Damn! This was a good quick lesson!
Thanks
Trying to make some notes here. Please point out my mistakes if I made any and I'll make corrections.
Service/type:ClusterIP: Each service has an IP from within the Kubernetes network, but not accessible from the outside.
Service/type:NodePort: Traffic goes to externally accessible IP, and then goes to the service-occupied port. But each service cannot have more than 1 port. Management of usable node IP list is also cumbersome.
Service/type:LoadBalancer: It creates a NLB (Network Load Balancer) for each service (usuaully hosted on cloud service provider) which is one-to-one mapped with service. Thus, many NLBs are required for many individual services, which results in low scalability.
↓
Ingress: Routes external request using a set of rules, dispatching them to services. It also comes with the capability to do TLS termination, virtual hosts, etc.
Do you know that there's a difference between object code and machine code ? OR that there are more than 13 types of pointers in c++ ? OR why stack frames are faster than heap frames ? OR the compiler can even reject your request for method inlining 🙄🙄 If not then checkout this repository for more such interesting facts and concepts -: https://github.com/Intangible-pg18/Cpp-Deep-Dive
Thanks for the nice explanation (and esp. of pointing to the "Kubernetes explained" in the beginning)! Looking forward to other informative videos.
thks a lot. I will share your video with my collegues. It was difficult to understand the differences between nodeport and ingress. It's easier with your explanation. One of my collegues said that it would be better to have one ingress per service. What do you think about it ?
Nicely explained. Can we please get a video on default and custom operators on Kubernetes?
3 view