Kubernetes Gardener

    This vendor-provided document has not been tested on the Istio 1.9 release and may contain bugs.

    To set up your own , see the documentation or have a look at the project. To learn more about this open source project, read the blog on kubernetes.io.

    1. If you already have kubectl CLI, run kubectl version --short to check the version. You need or newer. If your kubectl is older, follow the next step to install a newer version.

    1. using a kubeconfig. If you are not the Gardener Administrator already, you can create a technical user in the Gardener dashboard: go to the “Members” section and add a service account. You can then download the kubeconfig for your project. You can skip this step if you create your cluster using the user interface; it is only needed for programmatic access, make sure you set export KUBECONFIG=garden-my-project.yaml in your shell.

    You can create your cluster using kubectl cli by providing a cluster specification yaml file. You can find an example for GCP . Make sure the namespace matches that of your project. Then just apply the prepared so-called “shoot” cluster CRD with :

    You can now download the kubeconfig for your freshly created cluster in the Gardener dashboard or via cli as follows:

    This kubeconfig file has full administrators access to you cluster. For the rest of this guide be sure you have export KUBECONFIG=my-cluster.yaml set.

    Cleaning up

    Use the Gardener dashboard to delete your cluster, or execute the following with kubectl pointing to your garden-my-project.yaml kubeconfig: