Kubernetes / Storage, Configuration & Data Protection
Investigate a claim using the wrong default StorageClass
A claim without an explicit class can be provisioned differently across clusters or after default-class changes. Inspect class metadata and the actual claim.
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 storageclass
kubectl -n app get pvc app-data -o yamlRead the result
The listing identifies classes and default annotations through supported output; the claim records its selected class. Existing bindings are not automatically migrated by changing a default.
Resolve and verify
Compare the intended performance, topology and reclaim policy with the selected class. Correct future provisioning through the reviewed manifest and plan any data migration separately.
Before changing production
Do not change the cluster default for one workload without reviewing other namespaces and pending claims.