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
Graduate ReadWriteOncePod to GA #121077
Graduate ReadWriteOncePod to GA #121077
Conversation
@chrishenzie: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility. In response to this:
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/test-infra repository. |
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/test-infra repository. |
4572273
to
23d838c
Compare
23d838c
to
86aead1
Compare
86aead1
to
90d5449
Compare
Hi @chrishenzie from sig-scheduling, I think we have more places to remove this configuration, e.g.
agree? |
@kerthcet From my understanding the plan is to remove all feature gating logic two releases after GA. |
/assign kerthcet |
Were the E2E tests completed during beta? |
oh, I didn't know that, I thought since feature-gate GAed, we should remove all the related logics for we can't disable the feature anymore, like
|
90d5449
to
54df7a0
Compare
Yes they were. Updating in kubernetes/enhancements#4306. |
Please fix linter |
54df7a0
to
19ebcf4
Compare
/remove-sig node |
19ebcf4
to
2dbd405
Compare
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM fro sig-scheduling, so
/approve
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
as well :)
LGTM label has been added. Git tree hash: 72e79f69612b4262844068cb8d62a5f194f7ab21
|
/assign @msau42 @xing-yang (for sig-storage approval) |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, chrishenzie, kerthcet, msau42 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 |
@chrishenzie: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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/test-infra repository. I understand the commands that are listed here. |
/test pull-kubernetes-unit |
What type of PR is this?
/kind feature
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig storage
/sig scheduling
/milestone 1.29
/cc @msau42
/cc @alculquicondor