Skip to content
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

CustomResource should not instantiate spec / status #2828

Closed
iocanel opened this issue Feb 23, 2021 · 0 comments · Fixed by #2835 or jenkinsci/kubernetes-client-api-plugin#83
Closed
Assignees
Milestone

Comments

@iocanel
Copy link
Member

iocanel commented Feb 23, 2021

All Kubernetes resources when instantiated start with null values for Spec and Status, the same should be the case for CustomResource too.

And while in 99.9% of the cases the Spec will be initialized by the user (so no harm really done), that is not true about Status (where does not make sense for user created instances, but only for server created ones).

@manusa manusa added this to the 5.2.0 milestone Feb 23, 2021
@metacosm metacosm self-assigned this Feb 25, 2021
This was referenced Mar 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment