Kubernetes / Cluster Operations, Access & Incident Response
Investigate a missing Kubernetes resource kind through API discovery
A manifest can fail because its API version was removed, the resource is optional or a CRD is absent. Query what the server serves.
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 api-resources
kubectl api-versionsRead the result
These list discoverable resources and API versions for the current cluster and identity. Discovery caches and permissions can influence client behavior.
Resolve and verify
Compare the failing apiVersion and kind with the installed release and supported migration guide. Update the managed manifest or install an approved required API through its owner.
Before changing production
Do not restore obsolete API versions through unsupported flags or apply guessed manifests to production.