<p>I intend to add additional error message fields to a custom resource status. The fields are marked as</p>
<pre><code>ErrMsg string `json:&quot;errmsg,omitempty&quot;`
</code></pre>
<p>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?</p>

<p>According to <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#typical-status-properties" rel="nofollow noreferrer">this</a></p>
<blockquote>
<p>Additional fields may be added in the future.</p>
</blockquote>
<p>If your controller is only ever writing to status then you don't need to bump the CRD version.</p>
<p>It also depends what sort of validation you have on the CRD - like if the <a href="https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation" rel="nofollow noreferrer">structural schema</a> is validating the status.</p>
<p><a href="https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api_changes.md#multiple-api-versions" rel="nofollow noreferrer">Here</a> are conventions for multiple API versions (although there isn't much on <code>status</code>)</p>
