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

RBAC, cert-manager, etc. #48

Open
wants to merge 11 commits into
base: master
Choose a base branch
from
Open

RBAC, cert-manager, etc. #48

wants to merge 11 commits into from

Conversation

bartlettc22
Copy link
Collaborator

@bartlettc22 bartlettc22 commented May 14, 2019

  • Removing custom LetsEncrypt support in favor of CertManager
  • Fixes issue with dumb-init not running as PID 1 in the Vault deployment
  • Adding RBAC support
  • Additional TCP option support for Vault
  • Will now automatically roll deployments when Vault config changes
  • Made PodManagementPolicy optional for statefulsets to allow upgrading of older clusters

Addresses issue #47, #3

@bartlettc22 bartlettc22 mentioned this pull request May 14, 2019
* Adding RBAC support
* Additional TCP option support for Vault
* Will now automatically roll deployments when Vault config changes

Copy link
Contributor

Choose a reason for hiding this comment

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

The CertManger will be nice. Still can use letsEncrypt, but will now have something updating the 90-day certs.

cp /vault/config-ro/config.json /vault/config/config.json
docker-entrypoint.sh server
args:
- "server"
Copy link
Contributor

Choose a reason for hiding this comment

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

This is an important change. This will enable dumb-init to be process one again. Currently, Hashicorp Consul's helm doesn't do this correctly!

@@ -73,6 +75,9 @@ Vault:
DisableConsulRegistration: "false"
DefaultLeaseTtl: "768h"
MaxLeaseTtl: "768h"
# config:
# tcpAdditionalOptions: |
# tls_disable_client_certs = "true"
Copy link
Contributor

Choose a reason for hiding this comment

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

Doesn't this seem like it should be a default for Vault from Hashicorp? Many people noticed a chrome pop-up when opening the Vault web interface asking for them to select a client cert to continue with...

@thorix
Copy link
Contributor

thorix commented May 16, 2019

Overall this PR looks good. This PR has been tested and everything seems to be in order.

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.

2 participants