You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/services/gardener/README.md
+12-21Lines changed: 12 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ The InfraBox Garden Service can be used to dynamically provision a Kubernetes Cl
27
27
"maxNodes": 1,
28
28
"minNodes": 1,
29
29
"zone": "eu-central-1a",
30
-
"clusterVersion": "1.10",
30
+
"clusterVersion": "1.10"
31
31
}
32
32
}]
33
33
}]
@@ -79,31 +79,22 @@ kubectl get pods
79
79
80
80
## Install
81
81
To install the service in your Kubernetes cluster you have to first create a AWS Service Account and configure gardener to use it (secretBindingRef). Next, create a kubeconfig which this service will use to communicate with Gardener. Create a secret containing the kubeconfig:
The names of the secret and the secretBindingRef can be chosen arbitrarily. The service will read the names from the environment variables mentioned below. The name of the kubeconfig entry within the secret (`garden_kubeconfig`) is mandatory.
87
+
The names of the secret and the secretBindingRef can be chosen arbitrarily. The service will read the names from the environment variables mentioned below. The name of the kubeconfig entry within the secret (`garden_kubeconfig`) is mandatory.
88
+
89
+
Now use helm to install the Gardener Service. Edit values.yaml for specify the required values.
87
90
88
-
Now use helm to install the GCP Service.
91
+
Parameter | Description | Default | Required
92
+
--- | --- | --- | ---
93
+
`gardener.project` | Name of the Gardener Project | `nil` | yes
94
+
`gardener.namespace` | Name of the Gardener Namespace | `nil` | yes
95
+
`gardener.secret_binding_ref` | Name of the Gardener Secret binding ref| `nil` | yes
The garden-operator depends on several environment variables:
97
-
98
-
#### mandatory:
99
-
*`CRENDENTIALS_SECRET`: Name of the secret containing the kubeconfig for Gardener. Within the secret, the config must be stored under the name `garden_kubecfg`.
100
-
*`GARDEN_NAMESPACE` : The namespace within Gardener to create new shoot clusters in.
101
-
*`GARDENER_PROJECTNAME`: Name of the gardener project which will contain the generated clusters.
102
-
*`SECRET_BINDING_REF`: secretBindingRef as configured in Gardener.
103
-
104
-
#### optional
105
-
*`LOGLVL`: the logging level to use. Valid values are: `debug`, `info`, `warn`, `error`. default: `warn`.
106
-
*`AWS_MAINTENANCE_AUTOUPDATE`: boolean. Enables autoupdate of kubernetes. default: `true`.
107
-
*`AWS_MAINTENANCE_AUTOUPDATE_TWBEGIN`: Begin of the maintenance window. default: `220000+0100`. If used, must be set in conjunction with `AWS_MAINTENANCE_AUTOUPDATE_TWBEND`.
108
-
*`AWS_MAINTENANCE_AUTOUPDATE_TWBEND`: End of the maintenance window. default: `230000+0100`. If used, must be set in conjunction with `AWS_MAINTENANCE_AUTOUPDATE_TWBEGIN`.
0 commit comments