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

Support TLS with vault for the server-acl-init job #889

Merged
merged 5 commits into from
Dec 6, 2021

Conversation

ishustava
Copy link
Contributor

Changes proposed in this PR:

How I've tested this PR:
acceptance tests

How I expect reviewers to test this PR:
code review

Checklist:

  • Tests added
  • CHANGELOG entry added

    HashiCorp engineers only, community PRs should not add a changelog entry.
    Entries should use present tense (e.g. Add support for...)

@ishustava ishustava requested review from kschoche, a team and thisisnotashwin and removed request for a team December 2, 2021 15:47
Copy link
Contributor

@thisisnotashwin thisisnotashwin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💥 this is excellent!!

Copy link
Contributor

@kschoche kschoche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔥

@kschoche kschoche mentioned this pull request Dec 2, 2021
2 tasks
@kschoche kschoche mentioned this pull request Dec 3, 2021
2 tasks
ishustava and others added 4 commits December 6, 2021 14:34
* Support server TLS with vault for the server-acl-init job
* Support server TLS with vault for the sync catalog
* Support server TLS with vault for the client snapshot agent deployment (#891)
@kschoche kschoche merged commit 3d14200 into server-tls-bootstrapping Dec 6, 2021
@kschoche kschoche deleted the vault-tls-server-acl-init branch December 6, 2021 22:21
kschoche added a commit that referenced this pull request Dec 7, 2021
* Support Vault server running with TLS (#874)
* Change vault cluster in acceptance tests to only run with TLS. All tests will run against vault with TLS because that is the use case we think will be the most valuable for users to test
* Support adding Vault CA as a secret to pods that will be using vault agent. We need to add two annotations to pods:
      * vault.hashicorp.com/agent-extra-secret with the value of the vault CA secret name. The secret will be mounted to vault agent at /vault/custom path. See docs here
      * vault.hashicorp.com/ca-cert - with the path of the ca file inside the vault agent container. This should be /vault/custom/<secret key>
* Most pods will only need those annotations. The server pods also need the Vault CA secret to be mounted as a volume because it needs the CA to be on the file system for the vault connect CA provider.

* add terminating and ingress gateways TLS support (#894)
* Support TLS with vault for the server-acl-init job (#889)
* Support TLS with Vault for the sync catalog deployment (#890)
* Support server TLS with vault for the client snapshot agent deployment (#891)

Co-authored-by: Iryna Shustava <iryna@hashicorp.com>
Co-authored-by: Luke Kysow <1034429+lkysow@users.noreply.github.com>
rrondeau pushed a commit to rrondeau/consul-k8s that referenced this pull request Dec 21, 2021
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

Successfully merging this pull request may close these issues.

4 participants