Skip to content

Latest commit

 

History

History
30 lines (24 loc) · 1.49 KB

kubernetes.md

File metadata and controls

30 lines (24 loc) · 1.49 KB

Deploying the Gardener into a Kubernetes cluster

As already mentioned, the Gardener is designed to run as API server extension in an existing Kubernetes cluster. In order to deploy it, you require valid Kubernetes manifests. We use Helm in order to generate these manifests. The respective Helm chart for the Gardener can be found here. In order to deploy it, execute

# Check https://github.com/gardener/gardener/releases for current available releases.
RELEASE=0.19.1

# Since master can have breaking changes after last release, checkout the tag for your release
git checkout $RELEASE

cat <<EOF > gardener.values
global:
  apiserver:
    image:
      tag: $RELEASE
  controller:
    image:
      tag: $RELEASE
EOF

helm install charts/gardener \
  --namespace garden \
  --name gardener \
  -f gardener.values \
  --wait

You can check the default values file for other configuration values. Please note that all resources and deployments need to be created in the garden namespace (not overrideable).

⚠️ The Seed Kubernetes clusters need to have a nginx-ingress-controller deployed to make the Gardener work properly. Moreover, there should exist a DNS record *.ingress.<SEED-CLUSTER-DOMAIN> where <SEED-CLUSTER-DOMAIN> is the value of the ingressDomain field of a Seed cluster resource.