-
Notifications
You must be signed in to change notification settings - Fork 417
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
Update to custom field in custom resource condition is silently dropped #981
Comments
Is that in status? |
Yes, this is in status. |
You have to use |
Hey, if I understand it correctly, that is for the case where subresource is enabled. I have not enabled it for my resource. Also, other custom fields with string type can be updated just fine, so I wonder if it has anything to do with the data type. |
I don't see anything obviously wrong. If those fields also exist in the CRD that you have deployed, there should be no reason why the values should be dropped |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Hello,
I added a custom field to the condition field of my CRD that looks like the following:
I was hoping to keep track of some metadata along with the condition. However, it seems that when the condition was updated, the metadata field was silently dropped. I can verify with
kubectl edit
. The command went through without validation error, but the output of the new resource doesn't have the metadata field. Why is this?The text was updated successfully, but these errors were encountered: