-
Notifications
You must be signed in to change notification settings - Fork 40.9k
deflake storage tests: changing the name of non-namespaced items like ClusterRole with driver namespace as suffix #132695
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: carlory The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
/test pull-kubernetes-unit |
/kind failing-test |
We try to avoid referencing PRs in commit messages. Is the PR title right? (I would edit it) |
BTW, when Prow triggers a merge, the title of a PR becomes part of a commit message. |
Do we have that policy documented somewhere, including the rationale? Does the same apply to commit hashes? |
…terRole with driver namespace as suffix before create it Signed-off-by: carlory <baofa.fan@daocloud.io>
I changed it. |
What type of PR is this?
What this PR does / why we need it:
#129369 want to fix #118037 but it cause another flaky test when the test has a bad cleanup
so we can not remove the driver namespace before test namespace.
we need to change the generation policy of all non-namespaced resource for driver manifests.
Which issue(s) this PR is related to:
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: