kind

    • Please use the latest Go version.
    • To use kind, you will also need to .
    • Install the latest version of kind.
    • Increase Docker’s .
    1. Create a cluster with the following command:

      --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:

      1. istio-testing
    3. To list the local Kubernetes contexts, use the following command.

      1. $ kubectl config get-contexts
      2. CURRENT NAME CLUSTER AUTHINFO NAMESPACE
      3. minikube minikube minikube

      kind is prefixed to the context and cluster names, for example: kind-istio-testing

    4. 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:

    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 setup Dashboard for kind.

    1. To deploy Dashboard, run the following command:

      1. $ kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.1.0/aio/deploy/recommended.yaml
    2. Verify that Dashboard is deployed and running.

      1. $ kubectl create clusterrolebinding default-admin --clusterrole cluster-admin --serviceaccount=default:default
    3. To login to Dashboard, you need a Bearer Token. Use the following command to store the token in a variable.

      1. $ token=$(kubectl get secrets -o jsonpath="{.items[?(@.metadata.annotations['kubernetes\.io/service-account\.name']=='default')].data.token}"|base64 --decode)

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

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

      Click to view your deployments and services.

      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.