k8s: Fix secret shared between e2e tests #8648
Merged
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.
The flakynest in the following tests were caused by parallerisation runs:
Each tests tries to verify if secret reference for cloud storage config works as expected. Secret was put in default namespace with the same name. Now names changed to be dedicated per test.
Previously test reported the following log line in the operator logs:
https://buildkite.com/organizations/redpanda/analytics/suites/redpanda/runs/f60ee633-0997-40a5-8c50-80f0a48a8e8b
https://buildkite.com/organizations/redpanda/analytics/suites/redpanda/runs/746e89f0-5bff-4f83-ad34-cb00fcda4656
https://buildkite.com/organizations/redpanda/analytics/suites/redpanda/runs/7f203e10-fb6c-4ffd-9e48-9df82062ad94
Backports Required
UX Changes
None
Release Notes
Bug Fixes