Kind Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 43: | Line 43: | ||
kind load | kind load | ||
</syntaxhighlight> | </syntaxhighlight> | ||
<font color=darkkhaki>Is this necessary with a cluster-wide registry? See [Kind_Concepts#Registry|kind Registry]] and [[Kind_Concepts#Image_Handling|kind Image Handling]]</font> | <font color=darkkhaki>Is this necessary with a cluster-wide registry? See [[Kind_Concepts#Registry|kind Registry]] and [[Kind_Concepts#Image_Handling|kind Image Handling]]</font> | ||
Latest revision as of 23:58, 7 December 2023
Internal
Installation
brew install kind
Alternate installation instructions provided by YuniKorn developer documentation: https://yunikorn.apache.org/docs/next/developer_guide/env_setup/#local-kubernetes-cluster-with-kind
Cluster
See:
Create Cluster
This will bootstrap a Kubernetes cluster using a predefined node image.
export KIND_EXPERIMENTAL_PROVIDER=docker
kind create cluster
By default, the cluster is named "kind".
Upon creation, it can be listed with kind get clusters. Nodes can be listed with: kind get nodes.
Delete Cluster
kind delete cluster
Deleting cluster "kind" ...
Deleted nodes: ["kind-worker" "kind-control-plane"]
Get Clusters
kind get clusters
Nodes
Get Nodes
kind get nodes
Load Images into a Node
kind load
Is this necessary with a cluster-wide registry? See kind Registry and kind Image Handling