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

Incorrect assumption of StatefulSet name in server-acl-init #165

Closed
sbuzonas opened this issue Nov 16, 2019 · 2 comments · Fixed by #174
Closed

Incorrect assumption of StatefulSet name in server-acl-init #165

sbuzonas opened this issue Nov 16, 2019 · 2 comments · Fixed by #174
Labels
type/bug Something isn't working

Comments

@sbuzonas
Copy link

Wasn't sure if this was better reported in hashicorp/consul-helm or here

The server-acl-init subcommand assumes that the name of the StatefulSet will be {release_name}-consul-server

https://github.com/hashicorp/consul-k8s/blob/master/subcommand/server-acl-init/command.go#L143

The helm chart allows a user to specify a fullname override.
https://github.com/hashicorp/consul-helm/blob/v0.12.0/templates/_helpers.tpl#L8

Given the following configuration values.yaml provided to helm:

fullnameOverride: consul
global:
  bootstrapACLs: true

The StatefulSet will be named consul-server and the bootstrap job will fail

@sbuzonas
Copy link
Author

Created hashicorp/consul-helm#286 as a fix likely require updates to both

@lkysow lkysow added the type/bug Something isn't working label Dec 9, 2019
@lkysow
Copy link
Member

lkysow commented Dec 17, 2019

This is fixed in consul-helm v0.15.0. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants