I participated in Kubernetes Internal # 2

I participated in Kubernetes Internal # 2

Kubernetes Internal is a meetup that unravels the internal implementation of Kubernetes.

image.png

https://k8sinternal.connpass.com

Summary of points that I was personally interested in

Q1 Is there any material that summarizes the relationships between components?

A1. inductor Regarding the relevance of Kubernetes Component, ZLab's following material will be helpful. https://www.youtube.com/watch?v=_Bve-nkBr2E https://qiita.com/yuanying/items/ceeeb7329a4fdc566546

A1. bells17 For the overview diagram of Kubernetes Component, the official document will be helpful. https://kubernetes.io/docs/concepts/overview/components/

Q2 I think you often see the diagrams of kube-apiserver, controller-manager, and scheduler, but how do you organize and understand the relationships when cluster-autoscaler etc. comes out one step further?

A2. Inductor It's a good idea to watch a video of each component in a Kubecon maintainer session. You can ask the maintainer a question and it is recommended. For example, there are the following videos. https://www.youtube.com/watch?v=hoU79zapdYQ https://www.youtube.com/watch?v=OXSRfl8mYyo

Q3 I think that cloud-cotroller-manager and ACK are in the same position in the sense of wrapping Cloud from Kubernetes, but you can comment on their roles. Or

A3. Inductor ACK is an understanding of things like AWS Cloud Formation and terraform. There may be use cases when you want to manage the life cycle of AWS resources on the Kubernetes side. A similar predecessor is the Kubernetes Service Catalog (https://kubernetes.io/docs/concepts/extend-kubernetes/service-catalog/), but I don't know if it's maintained.

A3. bells17 AWS resources disappear as if you erased the data from etcd, so the operation may be a little difficult.

Q3 Personal supplement

I did some research on the service catalog It's not Kubernetes, but it seems that the Service Catalog is deprecated in Openshift 4 or later (Kubernetes 1.12 or later).

The service catalog is deprecated in OpenShift Container Platform 4. Equivalent and better functionality is present in the Operator Framework and Operator Lifecycle Manager (OLM).

Reference: https://docs.openshift.com/container-platform/4.1/applications/service_brokers/installing-service-catalog.html

The subsequent Operator Framework, which has better features than the Service Catalog, became the CNCF Incubating project in July of this year. https://www.cncf.io/blog/2020/07/09/toc-approves-operator-framework-as-incubating-project/

In fact, it seems that the Service Catalog will be abolished and integrated into the Operator Framework.

Recommended Posts

I participated in Kubernetes Internal # 2
I participated in JJUG CCC 2019 Spring
I participated in JJUG CCC 2019 fall
I participated in JJUG CCC 2019 Fall.
[Java] I participated in ABC-188 of Atcorder.
[* Java *] I participated in JJUG CCC 2019 Spring
I got stuck in File
I read module-info.java in java.base
Participated in JJUG CCC 2019 FALL
Stop apps (pods) in Kubernetes
I tried metaprogramming in Java
I sent an email in Java
I created a PDF in Java.
I wrote Goldbach's theorem in java
I tried putting Domino11 in CentOS7
Check Java parameters in Kubernetes pods
I made an annotation in Java.
I tried using JWT in Java