Full lesson
Explore the full explanation, examples, and visuals at your own pace.
Illustrative output, namespace shop
kubectl get all doesn't show all. Here, in namespace shop, it lists a Pod, a Service, a Deployment and a ReplicaSet. It's easy to look at that and assume the ConfigMap and Secret were never created. But that assumption can be wrong.
$ kubectl get all -n shop
NAME READY STATUS
pod/web-7d9f-x2k 1/1 Running
service/web ClusterIP
deployment.apps/web 1/1
replicaset.apps/web-7d9f 1/1Greyed items exist, but all skips them
Everything on the left exists in the namespace. But all is only a built-in group: workloads like Pods and Deployments, plus Services. ConfigMaps hold settings, Secrets hold sensitive values, and a PVC is a storage claim. They're real, just greyed out and skipped.
Fix: ask for the types by name
To see them, name the types yourself, separated by commas. Running kubectl get configmaps,secrets in the shop namespace lists web-config and web-secret, so they were created all along. The same pattern works for ingress and pvc.
$ kubectl get configmaps,secrets -n shop
NAME DATA
configmap/web-config 2
secret/web-secret 1
$ kubectl get ingress,pvc -n shopall means some. Ask for what you want by name.
All means some. Ask for what you want by name. If a type seems missing, query it directly before recreating anything.