K8SPG 798 remove watch secrets unit test#1183
Merged
Merged
Conversation
gkech
force-pushed
the
K8SPG-798-watch-secrets-unit-test
branch
3 times, most recently
from
June 25, 2025 10:26
ef605da to
b2939d6
Compare
gkech
force-pushed
the
K8SPG-798-watch-secrets-unit-test
branch
from
June 25, 2025 10:29
b2939d6 to
00f6a89
Compare
gkech
marked this pull request as ready for review
June 25, 2025 10:34
gkech
requested review from
egegunes,
hors,
nmarukovich and
pooknull
as code owners
June 25, 2025 10:34
egegunes
approved these changes
Jun 27, 2025
pooknull
approved these changes
Jun 27, 2025
Collaborator
commit: d312f17 |
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.
CHANGE DESCRIPTION
Problem:
The
Watching secretsenvtest that we maintain is very flaky. When it is failing it requires someone to retrigger it until it passes.The main reason for its failing is the assertions it performs for the reconcile count. In general we don't perform similar assertions to other parts of the codebase or in other operator (maybe I'm wrong here though). Also these assertions seem redundant for the test itself. So the proposal for this PR is to remove the test completely since it is not reliable and it's basic behaviour of updating secrets not unit test worthy by itself.
Cause:
Short explanation of the root cause of the issue if applicable.
Solution:
Short explanation of the solution we are providing with this PR.
CHECKLIST
Jira
Needs Doc) and QA (Needs QA)?Tests
Config/Logging/Testability