Kubernetes: Why does patching a CustomResourceDefinition /status subresource update the parent resource?

Question

I\'m trying to understand Kubernetes behaviour as it pertains to custom resources and their subresources -- specifically the status subresource.