-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Velero CRDs do not have subresources.status
#8285
Comments
This is by design. |
See also: #4972 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What steps did you take and what happened:
When writing code around Velero CRDs I noticed that I can not use
controller-runtime
StatusClient
with them. I get the following error:What did you expect to happen:
Developers are able to use
controller-runtime
StatusClient
with Velero CRDs.Anything else you would like to add:
Issue about similar problem that Velero itself is facing #6016
To fix the problem, just need to add the comment
+kubebuilder:subresource:status
in CRD generation code. Documentation reference: https://book.kubebuilder.io/reference/generating-crd#status🚨 This change, without other changes, may break Velero, as with it, it does not allow Spec and Status change together. But since it is a anti-pattern, it should be avoided.
Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: