Setting Ingress to use the active Vault Pod #257
Closed
Conversation
This file contains 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
Signed-off-by: Sean Johnson <sean@ttys0.net>
|
|
|
I came across this too but this solution is not good because it only creates the -active service if you're using ha. I made a change to achieve the same but with some extra logic. I'll put that PR up but I don't think this one should be accepted Sorry @ttyS0 . |
|
This PR achieves the same: #270 |
|
@georgekaz has a better approach. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Ingress service defaults to the
vaultservice which contains all the running Pods. For some operations, this can cause a error when astandbyPod happens to be connected to with the following message:Error [action description]: redirect would cause protocol downgrade.Since the chart creates a
vault-activeservice that points to the currently active Pod, this PR adds the-acvivesuffix to the service used by the Ingress so the active Pod is always being talked to by clients, which alleviates the above error.