magnum/releasenotes/notes/deploy-tiller-in-k8s-df12ee41d00dd7ff.yaml
Spyros Trigazis 0b5f4260d9 k8s_fedora: Deploy tiller
Add enable_tiller  label to install tiller in k8s_fedora_atomic
clusters. Defaults to false.

Add tiller_tag label to select the version of tiller. If the
tag is not set the tag that matches the helm client version in
the heat-agent will be picked.  The tiller image can be stored
in a private registry and the cluster can pull it using the
container_infra_prefix label.

Install tiller securely using helper container.

TODO:

*add instructions on how RBAC is designed
https://docs.helm.sh/using_helm/#example-deploy-tiller-in-a-namespace-restricted-to-deploying-resources-in-another-namespace
* add docs on how to install addon in the cluster using this tiller
* how users can get the creds to talk to tiller

NOTE:
The main goal of this tiller is internal usage!
Users can still deploy other tillers in other namespaces.

story: 2003902
task: 26780

Change-Id: I99d3a78085ba10030200f12bbfe58a72964e2326
Signed-off-by: dioguerra <dy090.guerra@gmail.com>
2019-02-11 11:18:08 +01:00

15 lines
763 B
YAML

---
features:
- |
Add tiller_enabled to install tiller in k8s_fedora_atomic
clusters. Defaults to false. Add tiller_tag label to select the
version of tiller. If the tag is not set the tag that matches the helm
client version in the heat-agent will be picked. The tiller image can
be stored in a private registry and the cluster can pull it using the
container_infra_prefix label. Add tiller_namespace label to select in
which namespace to install tiller. Tiller is install with a Kubernetes
job. This job runs with a container that includes the helm client.
This image is maintained by the magnum team and lives in,
docker.io/openstackmagnum/helm-client. This container follows the same
versions as helm and tiller.