From 35616bd0df6d46b1f988bfdbb1f39c80d75fda3e Mon Sep 17 00:00:00 2001 From: Matthew Fisher <matt.fisher@microsoft.com> Date: Mon, 27 Nov 2017 09:39:26 -0800 Subject: [PATCH] fix links to service_accounts.md --- docs/index.md | 2 +- docs/tiller_ssl.md | 2 +- docs/using_helm.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/index.md b/docs/index.md index a8e4ac483..4ca93bd1f 100644 --- a/docs/index.md +++ b/docs/index.md @@ -6,7 +6,7 @@ - [Frequently Asked Questions](install_faq.md) - [Using Helm](using_helm.md) - Learn the Helm tools - [Plugins](plugins.md) - - [Service Accounts for Tiller](service_accounts.md) - Apply RBACs to Tiller + - [Role-based Access Control](rbac.md) - [TLS/SSL for Helm and Tiller](tiller_ssl.md) - Use Helm-to-Tiller encryption - [Developing Charts](charts.md) - An introduction to chart development - [Chart Lifecycle Hooks](charts_hooks.md) diff --git a/docs/tiller_ssl.md b/docs/tiller_ssl.md index 59d653e26..71ddd8080 100644 --- a/docs/tiller_ssl.md +++ b/docs/tiller_ssl.md @@ -199,7 +199,7 @@ start up. If you want to customize the manifest, you can save that output to a file and then use `kubectl create` to load it into your cluster. -> We strongly recommend enabling RBAC on your cluster and adding [service accounts](service_accounts.md) +> We strongly recommend enabling RBAC on your cluster and adding [service accounts](rbac.md) > with RBACS. Otherwise, you can remove the `--dry-run` and `--debug` flags. We also recommend diff --git a/docs/using_helm.md b/docs/using_helm.md index 531cdac44..d2e1768a8 100755 --- a/docs/using_helm.md +++ b/docs/using_helm.md @@ -498,7 +498,7 @@ accepts chart source code, and (after audit) packages those for you. In some cases you may wish to scope Tiller or deploy multiple Tillers to a single cluster. Here are some best practices when operating in those circumstances. 1. Tiller can be [installed](install.md) into any namespace. By default, it is installed into kube-system. You can run multiple Tillers provided they each run in their own namespace. -2. Limiting Tiller to only be able to install into specific namespaces and/or resource types is controlled by Kubernetes [RBAC](https://kubernetes.io/docs/admin/authorization/rbac/) roles and rolebindings. You can add a service account to Tiller when configuring Helm via `helm init --service-account <NAME>`. You can find more information about that [here](service_accounts.md). +2. Limiting Tiller to only be able to install into specific namespaces and/or resource types is controlled by Kubernetes [RBAC](https://kubernetes.io/docs/admin/authorization/rbac/) roles and rolebindings. You can add a service account to Tiller when configuring Helm via `helm init --service-account <NAME>`. You can find more information about that [here](rbac.md). 3. Release names are unique PER TILLER INSTANCE. 4. Charts should only contain resources that exist in a single namespace. 5. It is not recommended to have multiple Tillers configured to manage resources in the same namespace. -- GitLab