Kind Concepts: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 15: | Line 15: | ||
=Registry Container Provider= | =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. | While initializing the cluster, the registry can use a different container provider, though usually there should be no good reason do so. | ||
=<span id='Node_Image'></span>"Node" Image= | =<span id='Node_Image'></span>"Node" Image= | ||
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
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