Config & Storage
Manage ConfigMaps, Secrets, PersistentVolumeClaims, and StorageClasses without the kubectl juggling.
Use Config & Storage to inspect the data sources and backing stores that workloads depend on.
ConfigMaps
Open a ConfigMap to review its keys, values, and YAML. Edit the object when you need to change configuration for an app. Dockerman checks the resource version before saving, so you get a conflict warning if someone else edited the same ConfigMap while you were working on it. Delete a ConfigMap from the list when it is no longer needed.
Editing a ConfigMap does not restart pods that mount it. Update the owning Deployment or StatefulSet if you need the new data to take effect.
Secrets
Open a Secret to inspect its type, keys, and values. The list shows common types such as Opaque, kubernetes.io/tls, and kubernetes.io/dockerconfigjson. The same resource-version conflict detection as ConfigMaps applies when editing.
Binary secret values can be downloaded to a local file. Delete a Secret from the list when it is no longer needed.
Reveal shows secret values in plaintext. Anyone who can see the screen at that moment can read them.
PersistentVolumeClaims
Use PersistentVolumeClaims to see the phase, bound PersistentVolume, storage class, access modes, and capacity for each claim. Delete a PVC from the list when the claim is released and no longer needed.
StorageClasses
Use StorageClasses to inspect the cluster's storage options, including the provisioner, reclaim policy, volume binding mode, and the default class marker.