Skip to content

Updating status of custom resource results in not found error #839

Answered by RVink
RVink asked this question in Q&A
Discussion options

You must be logged in to vote

Hi Buehler,

After doing some tests I found that I forgot to deploy an updated CRD. It simply was missing the subresources section, causing kubernetes to return the not found error.

Thanks for your help.

Ricardo

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@buehler
Comment options

@RVink
Comment options

@RVink
Comment options

Answer selected by RVink
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants