Skip to content

Latest commit

 

History

History
138 lines (100 loc) · 5.02 KB

kind.md

File metadata and controls

138 lines (100 loc) · 5.02 KB
Raw

Table of Contents generated with DocToc

kind - kubernetes in docker

kind provides the quickest way to set up clusters for use with the KubeFed control plane.

Download and Install kind

If you don't yet have kind installed, you can run the following script to download and install a known working version.

./scripts/download-e2e-binaries.sh

Make sure that your GOBIN directory is in your PATH as that is where kind will be installed. Your GOBIN directory should be at $(go env GOPATH)/bin:

Create Clusters

You can proceed to create clusters once you have kind available in your path.

Create Insecure Container Registry

Please answer the following question to determine if you need to set up an insecure container registry on your host:

  1. Are you planning on creating container images locally without pushing to a public container registry such as quay.io. For example, you can build your own custom image e.g. 172.17.0.1:5000/<imagename>:<tag>, as part of your development workflow and push to this container registry . See the development guide for more examples.

If you answered yes, then you will need to create an insecure container registry. Creating a container registry is necessary if you want your kind clusters to pull images that you built locally on your host without pushing them to a public container registry. See the docker docs for more details.

In order to create an insecure container registry, you can pass the CREATE_INSECURE_REGISTRY flag to create-clusters.sh as follows:

CREATE_INSECURE_REGISTRY=y ./scripts/create-clusters.sh

Configure Insecure Container Registry

Please answer the following questions to determine if you need to configure an insecure container registry on your host:

  1. Is this the first time you're running the create-clusters.sh script?
  2. Does your docker daemon need to be configured for an insecure container registry?

If you answered yes to both of these questions, then you will need to configure the docker daemon on your host for an insecure container registry. The reason for an insecure registry is to simplify the container registry setup by not enabling TLS. This only needs to be done once for a particular host. See the docker docs for more details.

In order to configure an insecure container registry, you can pass the CONFIGURE_INSECURE_REGISTRY_HOST flag to create-clusters.sh as shown below. The default container registry host is 172.17.0.1:5000 and needs to match the IP address of the default docker bridge on your host, typically 172.17.0.1. If you would like to change this then set the CONTAINER_REGISTRY_HOST="<host>:<port>" flag.

CONFIGURE_INSECURE_REGISTRY_HOST=y ./scripts/create-clusters.sh

This will automatically create the necessary dockerd daemon config and reload the docker daemon for you. Keep in mind that it will not do this for you if a config already exists, or your docker daemon is already configured with an --insecure-registry command line option.

If you would like to manually make the changes to your docker daemon instead, add 172.17.0.1:5000 as an insecure registry host and reload or restart your docker daemon. See the docker docs for more details.

Run Script

Run the following command to create 2 kind clusters:

./scripts/create-clusters.sh

The NUM_CLUSTERS is 2 by default. Set that variable before invoking the script if you'd like to change the default:

NUM_CLUSTERS=<num> ./scripts/create-clusters.sh

Delete Clusters

Delete Insecure Container Registry

Specify the DELETE_INSECURE_REGISTRY flag if you set up an insecure container registry and would like to have it deleted.

DELETE_INSECURE_REGISTRY=y ./scripts/delete-clusters.sh

Run Script

Run the following command to delete 2 kind clusters:

./scripts/delete-clusters.sh

The NUM_CLUSTERS is 2 by default. Set that variable before invoking the script if you'd like to change the default:

NUM_CLUSTERS=<num> ./scripts/delete-clusters.sh