Simplify teardown, hopefully making it more robust against CNO races#164
Merged
Conversation
Collaborator
Author
|
@vladbologa Your gut feeling was right -- the teardown was still susceptible to leaking of injected-cabundle configmap during teardown. |
AlexVulaj
reviewed
May 11, 2026
AlexVulaj
approved these changes
May 11, 2026
Collaborator
Author
|
🙏 |
Collaborator
Too late here, but I was thinking that maybe we could still have the old teardown behavior as a separate command, for the cases where the Operator teardown is broken? Something like |
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
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.
See #146 (comment) for context.
I think the complexity this adds and the difficulties in getting this robust in the presence of multiple concurent processes (RHACS Operator/Helm reconciler, CNO operator, roxie teardown), is not really worth it.