Reduce duplication and maintenance effort for kind Cluster specific…

…ation and `make` targets (gardener#6976)

* Add Helm chart for kind `Cluster` templating

* Drop duplicate `cluster-*.yaml` in favor or chart `values.yaml`

* `hack` scripts for `kind-{up,down}`

* `hack` script for `gardener-down`

docs/deployment/content/remote-local-setup.yaml

@@ -37,7 +37,7 @@ spec:
           echo 'source ~/.bashrc' > ~/.bash_profile
           cat > ~/.bashrc <<"EOF"
             export PATH=$PATH:/usr/local/go/bin
-            export KUBECONFIG=~/gardener/example/gardener-local/kind/kubeconfig:/tmp/kubeconfig-shoot-local.yaml
+            export KUBECONFIG=~/gardener/example/gardener-local/kind/local/kubeconfig:/tmp/kubeconfig-shoot-local.yaml
             source <(kubectl completion bash)
             alias k=kubectl
             complete -o default -F __start_kubectl k

docs/deployment/getting_started_locally.md

@@ -28,10 +28,10 @@ Based on [Skaffold](https://skaffold.dev/), the container images for all require
 make kind-up
 ```
 
-This command sets up a new KinD cluster named `gardener-local` and stores the kubeconfig in the `./example/gardener-local/kind/kubeconfig` file.
+This command sets up a new KinD cluster named `gardener-local` and stores the kubeconfig in the `./example/gardener-local/kind/local/kubeconfig` file.
 
 > It might be helpful to copy this file to `$HOME/.kube/config` since you will need to target this KinD cluster multiple times.
-Alternatively, make sure to set your `KUBECONFIG` environment variable to `./example/gardener-local/kind/kubeconfig` for all future steps via `export KUBECONFIG=example/gardener-local/kind/kubeconfig`.
+Alternatively, make sure to set your `KUBECONFIG` environment variable to `./example/gardener-local/kind/local/kubeconfig` for all future steps via `export KUBECONFIG=example/gardener-local/kind/local/kubeconfig`.
 
 All following steps assume that you are using this kubeconfig.
 
@@ -90,7 +90,7 @@ local   local          local      local    1.21.0        Awake         Create Pr
 (Optional): You could also execute a simple e2e test (creating and deleting a shoot) by running
 
 ```shell
-make test-e2e-local-simple KUBECONFIG="$PWD/example/gardener-local/kind/kubeconfig"
+make test-e2e-local-simple KUBECONFIG="$PWD/example/gardener-local/kind/local/kubeconfig"
 ```
 
 ### Accessing the `Shoot` cluster
@@ -140,15 +140,15 @@ There are cases where you would want to create a second cluster seed in your loc
 make kind2-up
 ```
 
-This command sets up a new KinD cluster named `gardener-local2` and stores its kubeconfig in the `./example/gardener-local/kind2/kubeconfig` file.
+This command sets up a new KinD cluster named `gardener-local2` and stores its kubeconfig in the `./example/gardener-local/kind/local2/kubeconfig` file.
 
 In order to deploy required resources in the KinD cluster that you just created, run:
 
 ```bash
 make gardenlet-kind2-up
 ```
 
-The following steps assume that you are using the kubeconfig that points to the `gardener-local` cluster (first KinD cluster): `export KUBECONFIG=example/gardener-local/kind/kubeconfig`.
+The following steps assume that you are using the kubeconfig that points to the `gardener-local` cluster (first KinD cluster): `export KUBECONFIG=example/gardener-local/kind/local/kubeconfig`.
 
 You can wait for the `local2` `Seed` to be ready by running:
 

docs/development/content/remote-local-setup.yaml

@@ -38,7 +38,7 @@ spec:
           cat > ~/.bashrc <<"EOF"
             export GOPATH=~/go
             export PATH=$PATH:/usr/local/go/bin
-            export KUBECONFIG=~/gardener/example/gardener-local/kind/kubeconfig:/tmp/kubeconfig-shoot-local.yaml
+            export KUBECONFIG=~/gardener/example/gardener-local/kind/local/kubeconfig:/tmp/kubeconfig-shoot-local.yaml
             source <(kubectl completion bash)
             alias k=kubectl
             complete -o default -F __start_kubectl k

docs/development/getting_started_locally.md

@@ -39,10 +39,10 @@ The Gardener components, however, will be run as regular processes on your machi
 make kind-up KIND_ENV=local
 ```
 
-This command sets up a new KinD cluster named `gardener-local` and stores the kubeconfig in the `./example/gardener-local/kind/kubeconfig` file.
+This command sets up a new KinD cluster named `gardener-local` and stores the kubeconfig in the `./example/gardener-local/kind/local/kubeconfig` file.
 
 > It might be helpful to copy this file to `$HOME/.kube/config` since you will need to target this KinD cluster multiple times.
-Alternatively, make sure to set your `KUBECONFIG` environment variable to `./example/gardener-local/kind/kubeconfig` for all future steps via `export KUBECONFIG=example/gardener-local/kind/kubeconfig`.
+Alternatively, make sure to set your `KUBECONFIG` environment variable to `./example/gardener-local/kind/local/kubeconfig` for all future steps via `export KUBECONFIG=example/gardener-local/kind/local/kubeconfig`.
 
 All following steps assume that you are using this kubeconfig.
 
@@ -135,7 +135,7 @@ local   local          local      local    1.21.0        Awake         Create Pr
 (Optional): You could also execute a simple e2e test (creating and deleting a shoot) by running
 
 ```shell
-make test-e2e-local-simple KUBECONFIG="$PWD/example/gardener-local/kind/kubeconfig"
+make test-e2e-local-simple KUBECONFIG="$PWD/example/gardener-local/kind/local/kubeconfig"
 ```
 
 When the shoot got successfully created you can access it as follows:
@@ -161,7 +161,7 @@ Next, setup the second KinD cluster:
 make kind2-up KIND_ENV=local
 ```
 
-This command sets up a new KinD cluster named `gardener-local2` and stores its kubeconfig in the `./example/gardener-local/kind2/kubeconfig` file. You will need this file when starting the `provider-local` extension controller for the second seed cluster.
+This command sets up a new KinD cluster named `gardener-local2` and stores its kubeconfig in the `./example/gardener-local/kind/local2/kubeconfig` file. You will need this file when starting the `provider-local` extension controller for the second seed cluster.
 
 ```bash
 make register-kind2-env                                           # registering the local2 seed
@@ -171,7 +171,7 @@ make start-gardenlet SEED_NAME=local2                             # starting gar
 In a new terminal pane, run
 
 ```bash
-export KUBECONFIG=./example/gardener-local/kind2/kubeconfig       # setting KUBECONFIG to point to second kind cluster
+export KUBECONFIG=./example/gardener-local/kind/local2/kubeconfig       # setting KUBECONFIG to point to second kind cluster
 make start-extension-provider-local \
   WEBHOOK_SERVER_PORT=9444 \
   WEBHOOK_CERT_DIR=/tmp/gardener-extension-provider-local2 \

docs/development/testing.md

@@ -228,7 +228,7 @@ Run an `envtest` suite (not using `gardener-apiserver`) against an existing clus
 
 ```bash
 make kind-up
-export KUBECONFIG=$PWD/example/gardener-local/kind/kubeconfig
+export KUBECONFIG=$PWD/example/gardener-local/kind/local/kubeconfig
 export USE_EXISTING_CLUSTER=true
 
 # run test with verbose output
@@ -242,7 +242,7 @@ Run a `gardenerenvtest` suite (using `gardener-apiserver`) against an existing g
 
 ```bash
 make kind-up
-export KUBECONFIG=$PWD/example/gardener-local/kind/kubeconfig
+export KUBECONFIG=$PWD/example/gardener-local/kind/local/kubeconfig
 make dev-setup
 # you might need to disable some admission plugins in hack/local-development/start-apiserver
 # via --disable-admission-plugins depending on the test suite
@@ -268,7 +268,7 @@ ginkgo build ./test/integration/resourcemanager/health
 
 # prepare a cluster to run the test against
 make kind-up
-export KUBECONFIG=$PWD/example/gardener-local/kind/kubeconfig
+export KUBECONFIG=$PWD/example/gardener-local/kind/local/kubeconfig
 export USE_EXISTING_CLUSTER=true
 
 # use same timeout settings like in CI
@@ -287,7 +287,7 @@ ginkgo build ./test/integration/controllermanager/bastion
 
 # prepare a cluster including gardener-apiserver to run the test against
 make kind-up
-export KUBECONFIG=$PWD/example/gardener-local/kind/kubeconfig
+export KUBECONFIG=$PWD/example/gardener-local/kind/local/kubeconfig
 make dev-setup
 # you might need to disable some admission plugins in hack/local-development/start-apiserver
 # via --disable-admission-plugins depending on the test suite
@@ -374,7 +374,7 @@ You can also run these tests on your development machine, using the following co
 
 ```bash
 make kind-up
-export KUBECONFIG=$PWD/example/gardener-local/kind/kubeconfig
+export KUBECONFIG=$PWD/example/gardener-local/kind/local/kubeconfig
 make gardener-up
 make test-e2e-local  # alternatively: make test-e2e-local-simple
 ```