Library staff try kubectl get on a custom resource and fail until t…

Question

Library staff try kubectl get on a custom resource and fail until the matching CRD is installed. What rule explains that behavior?

Accepted Answer

CR instances require the CRD (API extension) to exist before the API serves that kind — You cannot file a “special permit” form before city hall adds that form to the catalog. Same with Kubernetes: install the CRD first, then create instances. kubectl cannot invent kinds out of thin air.

Answer

Custom resources are stored only on worker local disk until CNI is ready

Answer

kubectl can invent arbitrary kinds without CRDs if the kubeconfig uses impersonation

Answer

Operators delete CRDs automatically before any custom resource may be created

Library staff try kubectl get on a custom resource and fail until the matching CRD is installed. What rule explains that behavior?

Short Explanation

Full Explanation