gruntwork-io/kubergrunt
View on GitHubEnhance `README.md` with commands for creating resources
Open
#26 opened on Feb 7, 2019
good first issue
Repository metrics
- Stars
- (564 stars)
- PR merge metrics
- (PR metrics pending)
Description
Hi Yori,
I was trying to use Kubergrunt to deploy Helm to a GKE cluster. Would it make sense to add a few lines to the README.md file to illustrate how to create a dedicated ServiceAccount and namespace for Helm.
e.g:
❯ kubectl create namespace tiller-world
namespace "tiller-world" created
❯ kubectl create serviceaccount tiller --namespace tiller-world
serviceaccount "tiller" created
That way the user can get started quicker and avoid errors like: ERROR: namespaces "tiller-world" not found if they then run:
kubergrunt helm deploy \
--tiller-namespace tiller-world \
--resource-namespace dev \
--service-account tiller \
--tls-common-name tiller \
--tls-org Gruntwork \
--tls-org-unit IT \
--tls-city Phoenix \
--tls-state AZ \
--tls-country US \
--rbac-group admin \
--client-tls-common-name admin \
--client-tls-org Gruntwork
It also removes the ambiguity from the following statement:
Note: This command does not create Namespaces or ServiceAccounts, delegating that responsibility to other systems.