[8.x](backport #2986) [Go] Fix a flaky Kubernetes test setup #2992
+2
−2
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.
Summary of your changes
One of the k8s suite tests was flaky. In case a valid
kubeconfig
is present on the machine that runs the test, the suite will fail, getting the data from defaultkubeconfig
path. As a solution, I set theKubeConfig
path to something non-existent to ensure we get the expected result and truekubeconfig
does not interfere.Screenshot/Data
The test failing before the fix; Please note an actual cluster name from my
kubeconfig
:production
.Related Issues
None, found randomly on my machine.
This is an automatic backport of pull request #2986 done by [Mergify](https://mergify.com).