<p>As an example, if I define a CRD of <code>kind: Animal</code>, can I define a CRD, <code>Dog</code>, as a specific <code>type</code> of <code>Animal</code>? The <code>Dog</code> CRD would have a different/extended schema requirement than the base <code>Animal</code> CRD. </p>

<p>My goal here is to be able to do a <code>kubectl get animals</code> and be able to see all the different <code>type</code>'s of <code>Animals</code> that were created. </p>

<p>This seems to have been achieved by using the <code>type</code> metadata for certain resources like <code>Secret</code>, but I can't seem to find how to achieve this with a CRD. </p>

<p><strong>Note</strong>: my real use case isn't around storing <code>Animals</code>, but, it's just a typical example from OOP.</p>

<p>No, this is not a feature of Kubernetes. All Secret objects are of the same Kind, and Type is just a string field.</p>
