Kind Concepts: Difference between revisions
Line 6: | Line 6: | ||
=Cluster= | =Cluster= | ||
A Kubernetes cluster can be created with <code>[[Kind_Operations#Create_Cluster|kind create cluster]]</code>. The "nodes" are implemented as Docker containers. Upon creation of a default cluster, it will report two nodes, "kind-control-plane" and "kind-worker". The corresponding Docker containers are: | |||
<font size=-2> | |||
CONTAINER ID IMAGE [...] NAMES | |||
3108457ff1b6 [...]/kind:v1.27.3-3966ac76 kind-worker | |||
c90cb24cc040 [...]kind:v1.27.3-3966ac76 kind-control-plane | |||
2702defb0752 [...]/registry:2 kind-registry | |||
</font> | |||
Other container providers can be used, and in that case, the nodes/containers will be reported differently. | |||
=Cluster Container Provider= | =Cluster Container Provider= | ||
While initializing the cluster, the initialization process will report what container provider it is using. | While initializing the cluster, the initialization process will report what container provider it is using. |
Revision as of 22:50, 7 December 2023
Internal
Overview
kind
is a tool for running local Kubernetes clusters using Docker container as cluster nodes. As such, it needs a Docker installation to run and it is similar to Docker Desktop in that respect. kind was primarily designed for testing Kubernetes itself, but may be used for local development or CI.
Cluster
A Kubernetes cluster can be created with kind create cluster
. The "nodes" are implemented as Docker containers. Upon creation of a default cluster, it will report two nodes, "kind-control-plane" and "kind-worker". The corresponding Docker containers are:
CONTAINER ID IMAGE [...] NAMES 3108457ff1b6 [...]/kind:v1.27.3-3966ac76 kind-worker c90cb24cc040 [...]kind:v1.27.3-3966ac76 kind-control-plane 2702defb0752 [...]/registry:2 kind-registry
Other container providers can be used, and in that case, the nodes/containers will be reported differently.
Cluster Container Provider
While initializing the cluster, the initialization process will report what container provider it is using.
KIND_EXPERIMENTAL_PROVIDER
Registry
Registry Server
Registry Container Provider
While initializing the cluster, the registry can use a different container provider, though usually there should be no good reason do so.
"Node" Image
The “node” image is a Docker image for running nested containers, systemd, and Kubernetes components.
Node Provider
Loading Images
TODO https://yunikorn.apache.org/docs/next/developer_guide/env_setup/#loading-your-images