Skip to content

vault: Reference controller IP for backend TLS certificates #1283

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

Merged
merged 1 commit into from
Sep 12, 2024

Conversation

bbezak
Copy link
Member

@bbezak bbezak commented Sep 12, 2024

change [1] introduced regression for fix made in [2], as vault is not running on network nodes

[1] f593df7#diff-75d94f901ed6a58cc592a524e6d2ecc9c1ad2826f3f7c6ebaf95a0aa045d8d71R21
[2] af0d013

@bbezak bbezak requested a review from a team as a code owner September 12, 2024 08:30
@bbezak bbezak changed the title Reference controller IP for backend TLS certificates vault: Reference controller IP for backend TLS certificates Sep 12, 2024
@markgoddard markgoddard merged commit e474210 into stackhpc/2023.1 Sep 12, 2024
12 checks passed
@markgoddard markgoddard deleted the vault-backend-network-node branch September 12, 2024 08:43
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