-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
When the clusterresourcesetbinding is v1beta2, set the clusterName field to be required. #8267
Comments
/triage accepted Thanks for following up with this! |
Hey @chaunceyjiang I would like to work on this issue however this being my first issue for the repo is there anything I should be aware about the issue which is not mentioned here or in the link provided? Thanks in advance |
I think we cannot work on this issue yet as we have to wait unti our APIs are bumped to v1beta2. This could take a few months or years :) |
Opps! I got into the desription and forgot to see the main point :) |
This issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
/triage accepted |
/lifecycle frozen |
/priority important-longterm |
What would you like to be added (User Story)?
When the clusterresourcesetbinding is v1beta2, set the clusterName field to be required.
Detailed Description
refer to #7680 (comment)
Anything else you would like to add?
No response
Label(s) to be applied
/kind feature
The text was updated successfully, but these errors were encountered: