From 22872b03a6985cad1f1b1d642b30bf673663b622 Mon Sep 17 00:00:00 2001 From: Iryna Shustava Date: Tue, 28 Jan 2020 22:18:12 -0800 Subject: [PATCH] docs: Clarify the use of kustomize or ship with the Helm chart (#7154) --- website/source/docs/platform/k8s/helm.html.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/website/source/docs/platform/k8s/helm.html.md b/website/source/docs/platform/k8s/helm.html.md index 46aeaf1dea..3dd879c1c5 100644 --- a/website/source/docs/platform/k8s/helm.html.md +++ b/website/source/docs/platform/k8s/helm.html.md @@ -401,4 +401,8 @@ connectInject: Consul within Kubernetes is highly configurable and the Helm chart contains dozens of the most commonly used configuration options. -If you need to extend the Helm chart with additional options, we recommend using a third-party tool, such as [kustomize](https://github.com/kubernetes-sigs/kustomize) or [ship](https://github.com/replicatedhq/ship). +If you need to extend the Helm chart with additional options, we recommend using a third-party tool, +such as [kustomize](https://github.com/kubernetes-sigs/kustomize) or [ship](https://github.com/replicatedhq/ship). +Note that the Helm chart heavily relies on Helm lifecycle hooks, and so features like bootstrapping ACLs or TLS +will not work as expected. Additionally, we can make changes to the internal implementation (e.g., renaming template files) that +may be backward incompatible with such customizations.