Add Vault redundancy zones support #1170
Open
husunal wants to merge 9 commits intohashicorp:mainfrom
Open
Conversation
…Labels admission controller
…in HCL and JSON formats
husunal
force-pushed
the
redundancy-zones
branch
from
a0715de to
bdd1ffd
Compare
…n gating The notes.bats tests use `helm install --dry-run`, which contacts the Kubernetes API server and fails in the unit test CI pipeline where no cluster is available. Move the file to test/acceptance/ and gate each test on Kubernetes >= 1.35 to match the redundancy zones requirement. Co-authored-by: vijayavelsekar <vsekar@hashicorp.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Kubernetes 1.35+ can now expose node topology labels to pods via the Downward API (KEP-4742). This MR uses that Kubernetes-native feature to add Vault Enterprise redundancy zone support, so users can deploy Vault clusters the HashiCorp-recommended way for better availability and fault tolerance across zones.
Tested on GKE
1.35.0-gke.1403000cluster to validate end-to-end functionality.Requirements:
Related issue: #1053
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.