What is Kubernetes — Open Standards ?

#k8s #kubernetes #openstandard #learnwithfun

What is Kubernetes — Open Standards

Let us understand with real basic example that everyone of us came across ….

Why do we required school uniform ?

Uniforms help them stand out of the crowd so that they can be easily recognizable and also distinguish them for the service they do.
School uniform is the same set of clothes that every student of the school wears when he/she gets ready for school. Every school has its own sets of school uniforms, it can be one or more than it. The school dress of every school varies from the other school as it is one of the ways to identify the children according to their clothes. It is easy to recognize which child is studying in which school according to their uniforms.

Uni-formality keep standardization of the school

That’s where kubernetes standards comes into the picture.
Now , Lets have quick information on Kubernetes Open Standard ?

Kubernetes standard also kind School uniforms which bring Uni-formality & standardization in the following areas of Kubernetes like Container Runtime, Storage, Networking, Service Mesh and Cloud Provider Interfaces etc.

CRI :- The Container Runtime Interface is a plugin interface which enables the kubelet to use a wide variety of container runtimes, without having a need to recompile the cluster components.
The Container Runtime Interface (CRI) is the main protocol for the communication between the kubelet and Container Runtime.
The Kubernetes Container Runtime Interface (CRI) defines the main gRPC protocol for the communication between the cluster components kubelet and container runtime.
Here most used Container Runtimes.
Containerd
CRI-O
Docker Engine
Mirantis Container Runtime

CNI :- Container Network Interface (CNI) is a framework for dynamically configuring networking resources. It uses a group of libraries and specifications written in Go. The plugin specification defines an interface for configuring the network, provisioning IP addresses, and maintaining connectivity with multiple hosts.
When used with Kubernetes, CNI can integrate smoothly with the kubelet to enable the use of an overlay or underlay network to automatically configure the network between pods. Overlay networks encapsulate network traffic using a virtual interface such as Virtual Extensible LAN (VXLAN). Underlay networks work at the physical level and comprise switches and routers.
CNI was created to make networking solutions integratable with a range of container orchestration systems and runtimes. Instead of making the networking solutions plug-gable, it defines a common interface standard for both the networking and container execution layers.
Here are list of current of the Container Network Provider.
Canal
Flannel
Calico
Weave
& many more @ https://kops.sigs.k8s.io/networking/

CSI :- CSI is an implementation of the Container Storage Interface specification, which offers a standardized mechanism for establishing connectivity between container orchestration tools and storage systems.
To facilitate the process, the storage vendor must provide a CSI-compliant volume driver that interacts with the CO plugin. Together, the driver and plugin enable the containerized workloads to support operations such as attaching or detaching volumes, mounting or unmounting volumes, and dynamically provisioning or deprovisioning volumes. Because the CSI specification standardizes the interface, a vendor needs to develop only one driver that works with any CSI-compliant CO plugin.
AWS Elastic Block Storage
Azure Blob
Azure Disk
GCE Persistent Disk
Google Cloud Storage
GlusterFS
Portworx
And many more in the list here https://kubernetes-csi.github.io/docs/drivers.html

SMI :- Service Mesh Interface is standard for Traffic Management, Traffic Policy & Traffic Telemetry on Kubernetes.
The Service Mesh Interface (SMI) is a specification for service meshes, with a focus on those that run on Kubernetes. It defines a common standard that can be implemented by a variety of providers. This allows for both standardization for end-users and innovation by providers of Service Mesh Technology. SMI enables flexibility and interoperability, and covers the most common service mesh capabilities.

CPI :- The Cloud Provider Interface (CPI) replaces the Kubernetes Controller Manager for only the cloud specific control loops. The Cloud Provider breaks away some of the functionality of Kubernetes controller manager (KCM) and handles it separately. Note that in many cases, some of these interfaces are not relevant for some CPIs, so you may only see a subset of these interfaces implemented for your cloud provider.

Note :- All the Kubernetes respective standard information extracted from Internet.

👉 Follow me Kiran Salunke on LinkedIn for professional networking
👉 Follow Cloudnloud Tech Community for more insightful knowledge & resources
👉 Follow Community YouTube channel https://lnkd.in/eXKJtvDH

Technology Inspirers
💪
Vijayabalan Balakrishnan
💪