Kubernetes / Cluster Operations, Access & Incident Response
Check a CRD's establishment before troubleshooting its custom objects
A custom controller cannot manage resources the API has not established successfully. Inspect CRD conditions and served versions.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl get crd widgets.example.com -o yamlRead the result
Replace the example with the actual CRD. Conditions, versions and conversion configuration help explain discovery or admission failures.
Resolve and verify
Compare the installed CRD and controller versions with the vendor's supported release. Repair schema or conversion-service dependencies through the owning operator.
Before changing production
Do not delete a CRD as a reinstall shortcut; deletion can remove its custom resources and associated state.