🐛 Fix CSR for ConstantBareMetalHostname #1295
Merged
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
|
@kranurag7 can you test this and check whether |
janiskemper
reviewed
May 6, 2024
janiskemper
reviewed
May 6, 2024
syself-bot
bot
added
the
size/M
guettli
force-pushed
the
tg/csr-for-constant-hostnames
branch
from
c3da8ae
to
ff21b8f
Compare
kranurag7
approved these changes
May 7, 2024
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.
What this PR does / why we need it:
If a cluster uses ConstantBareMetalHostname, then the CSRs were not approved, since the node-name
did not match the expected pattern.
This PR extends the CSR approving, so that CSRs for constant bm hostnames get approved.