Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

helm: Support a pre-set bootstrap ACL token #657

Closed
lkysow opened this issue Jan 22, 2021 · 4 comments
Closed

helm: Support a pre-set bootstrap ACL token #657

lkysow opened this issue Jan 22, 2021 · 4 comments

Comments

@lkysow
Copy link
Member

lkysow commented Jan 22, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

We currently support the following use case with Consul K8s:

If I have a Consul cluster, I can manually bootstrap ACLs and extract the boostrap token into a Kubernetes secret (i.e. create a Kubernetes secret manually after consul acl bootstrap).

However, the following use case is what this feature request is tracking:

I don't have a Consul cluster yet and I want to start one with bootstrap token defined via a String value. Could we support setting the master token ahead of time prior to the installation? For example if global.acls.bootstrapToken was set to a secret we would use the value in the secret.

@lkysow
Copy link
Member Author

lkysow commented Jan 22, 2021

Note: the api we use to bootstrap ACLs doesn't support setting the bootstrap key so we'd need to take that secret and set it as the value of the acl_tokens_master key in each server config.

@t-eckert t-eckert changed the title Support a pre-set bootstrap ACL token helm:Support a pre-set bootstrap ACL token Aug 24, 2021
@t-eckert t-eckert transferred this issue from hashicorp/consul-helm Aug 24, 2021
@david-yu
Copy link
Contributor

This has already been implemented and documented here: https://www.consul.io/docs/k8s/helm#v-global-acls-bootstraptoken

@david-yu
Copy link
Contributor

Re-opening since I was mistaken, revised the description based on further discussion.

@david-yu david-yu reopened this Oct 12, 2021
@david-yu david-yu changed the title helm:Support a pre-set bootstrap ACL token helm: Support a pre-set bootstrap ACL token Oct 12, 2021
@david-yu
Copy link
Contributor

david-yu commented Mar 7, 2022

Closing as this is partially addressed via #1061, where Vault is used as the secrets backend to specify a pre-set bootstrap ACL token. This support was built for Vault since setting a pre-set bootstrap token via String is what works well with a KV secrets engine like Vault. If a more generic solution is needed please open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants