-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
CustomResource should not instantiate spec / status #2828
iocanel opened this issue
Feb 23, 2021
· 0 comments
· Fixed by #2835 or jenkinsci/kubernetes-client-api-plugin#83
Milestone
Comments
11 tasks
metacosm
added a commit
that referenced
this issue
Feb 25, 2021
11 tasks
11 tasks
manusa
pushed a commit
that referenced
this issue
Mar 3, 2021
This was referenced Mar 12, 2021
This was referenced Mar 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
All Kubernetes resources when instantiated start with
null
values forSpec
andStatus
, the same should be the case forCustomResource
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 aboutStatus
(where does not make sense for user created instances, but only for server created ones).The text was updated successfully, but these errors were encountered: