istio.io/content/en/docs/setup/platform-setup/kind/index.md

title	description	weight	skip_seealso	keywords	owner	test
kind	Instructions to set up kind for Istio.	30	true	platform-setup kubernetes kind	istio/wg-environments-maintainers	no

kind is a tool for running local Kubernetes clusters using Docker container nodes. kind was primarily designed for testing Kubernetes itself, but may be used for local development or CI. Follow these instructions to prepare a kind cluster for Istio installation.

Prerequisites

• Please use the latest Go version.
• To use kind, you will also need to install docker.
• Install the latest version of kind.
• Increase Docker's memory limit.

Installation steps

1. Create a cluster with the following command:

   {{< text bash >}} $ kind create cluster --name istio-testing {{< /text >}}

   --name is used to assign a specific name to the cluster. By default, the cluster will be given the name "kind".

2. To see the list of kind clusters, use the following command:

   {{< text bash >}} $ kind get clusters istio-testing {{< /text >}}

3. To list the local Kubernetes contexts, use the following command.

   {{< text bash >}} $ kubectl config get-contexts CURRENT NAME CLUSTER AUTHINFO NAMESPACE

   •     kind-istio-testing   kind-istio-testing   kind-istio-testing
         minikube             minikube             minikube
     

   {{< /text >}}

   {{< tip >}} kind is prefixed to the context and cluster names, for example: kind-istio-testing {{< /tip >}}

4. If you run multiple clusters, you need to choose which cluster kubectl talks to. You can set a default cluster for kubectl by setting the current context in the Kubernetes kubeconfig file. Additionally you can run following command to set the current context for kubectl.

   {{< text bash >}} $ kubectl config use-context kind-istio-testing Switched to context "kind-istio-testing". {{< /text >}}

   Once you are done setting up a kind cluster, you can proceed to install Istio on it.

5. When you are done experimenting and you want to delete the existing cluster, use the following command:

   {{< text bash >}} $ kind delete cluster --name istio-testing Deleting cluster "istio-testing" ... {{< /text >}}

Setup Dashboard UI for kind

kind does not have a built in Dashboard UI like minikube. But you can still setup Dashboard, a web based Kubernetes UI, to view your cluster. Follow these instructions to set up Dashboard for kind.

1. To deploy Dashboard, run the following command:

   {{< text bash >}} $ kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml {{< /text >}}

2. Verify that Dashboard is deployed and running.

   {{< text bash >}} $ kubectl get pod -n kubernetes-dashboard NAME READY STATUS RESTARTS AGE dashboard-metrics-scraper-76585494d8-zdb66 1/1 Running 0 39s kubernetes-dashboard-b7ffbc8cb-zl8zg 1/1 Running 0 39s {{< /text >}}

3. Create a ServiceAccount and ClusterRoleBinding to provide admin access to the newly created cluster.

   {{< text bash >}} $ kubectl create serviceaccount -n kubernetes-dashboard admin-user $ kubectl create clusterrolebinding -n kubernetes-dashboard admin-user --clusterrole cluster-admin --serviceaccount=kubernetes-dashboard:admin-user {{< /text >}}

4. To login to Dashboard, you need a Bearer Token. Use the following command to store the token in a variable.

   {{< text bash >}} token=(kubectl -n kubernetes-dashboard create token admin-user) {{< /text >}}

   Display the token using the echo command and copy it to use for logging into Dashboard.

   {{< text bash >}} $ echo $token {{< /text >}}

5. You can Access Dashboard using the kubectl command-line tool by running the following command:

   {{< text bash >}} $ kubectl proxy Starting to serve on 127.0.0.1:8001 {{< /text >}}

   Click Kubernetes Dashboard to view your deployments and services.

   {{< warning >}} You have to save your token somewhere, otherwise you have to run step number 4 everytime you need a token to login to your Dashboard. {{< /warning >}}