-
Notifications
You must be signed in to change notification settings - Fork 326
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
Add support for Enterprise License to be configured in Vault #1032
Conversation
I'm most curious to talk through the VolumeMounts, how I should assume they will work, and whether those need to be modified. |
I've also found these failure validations for gossipEncryption key that I also implemented for enterpriseLicense in this PR. This has caused these two tests to fail. So, I amwondering:
|
29628f3
to
a48d018
Compare
57eeab2
to
3516257
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking pretty good, John! I left some comments in-line.
82f9f48
to
6977124
Compare
….secretName and secretKey
… to come from vault
…n also come from Vault.
…ce of either both or neither enterprise license secretKey and secretName.
…g either secretKey or secretName when the other is supplied
…retKey are provided when one of them is provided.
…se License on vault
…itional based on -enable-enterprise
…est. Adding failure logic to client-daemonset.yaml if secretName or secretKey is missing if one of them is already supplied.
…ce chart will fail when both are not supplied.
0d765e2
to
6d483ee
Compare
…hat we can conditionally add consul-enterprise licence policy to the Vault Auth Roles.
6d483ee
to
cb6c3f8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple more comments about tests, but otherwise looks good!
…terpriseLicense.secretKey or secretName is supplied.
d8562cb
to
172401f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hashicorp#1032) * update the wording for the consul sidecar to reflect current behaviour Co-authored-by: Nitya Dhanushkodi <nitya@hashicorp.com>
Changes proposed in this PR:
For server-statefulset, client-agent-snapshot-deployment, and client-daemonset:
How I've tested this PR:
How I expect reviewers to test this PR:
Checklist: