Use uncached client in the name registry integration test #2729
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
The name registry is an utility that is used in the context of controllers which in case of outdated cache just retry reconciliation. However, the integration test is not such a context, therefore using a caching client does not make sense. Furthermore, doing so could cause flakes due to a cache miss, for example https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-tests-main/builds/950
georgethebeatle
approved these changes
Aug 1, 2023
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.
Is there a related GitHub Issue?
No
What is this change about?
Use uncached client in the name registry integration test
The name registry is an utility that is used in the context of
controllers which in case of outdated cache just retry reconciliation.
However, the integration test is not such a context, therefore using a
caching client does not make sense. Furthermore, doing so could cause
flakes due to a cache miss, for example https://ci.korifi.cf-app.com/teams/main/pipelines/main/jobs/run-tests-main/builds/950
Does this PR introduce a breaking change?
No
Acceptance Steps
N/A