Create statefulset even on cert update failure #1981
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
cniackz
requested review from
jiuker,
pjuarezd,
dvaldivia and
harshavardhana
pjuarezd
approved these changes
Feb 12, 2024
dvaldivia
approved these changes
Feb 12, 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.
Objective:
To be able to create statefulset even if there is an error when updating the certificate
User Story:
We got stuck waiting for the
sswhile applyingcert-manager. Just notify the issue but create thessno matter what.Additional info:
This isn't necessarily a problem since we've merged this PR: #1847.
Scenario:
When a user deletes the StatefulSet, we no longer see any pods, making it difficult to identify the issue. We would prefer encountering a TLS issue in the Minio logs that we can resolve with an external certificate rather than being stuck without a StatefulSet.