kuberneteskubernetes-custom-resources

Kubernetes: does extending the status subresource require a new API version?

I intend to add additional error message fields to a custom resource status. The fields are marked as

ErrMsg string `json:"errmsg,omitempty"`

Does adding these fields require a new API version, or is is safe to just change the managing operator to fill these fields with values?

Solution

  • According to this

    Additional fields may be added in the future.

    If your controller is only ever writing to status then you don't need to bump the CRD version.

    It also depends what sort of validation you have on the CRD - like if the structural schema is validating the status.

    Here are conventions for multiple API versions (although there isn't much on status)