ConfigMap as volume

General Discussions
1

Hi,
I have ConfigMap:

kind: ConfigMap
metadata:
  name: curator

And I mount this as volume to my deployment:

        - name: config-volume
          mountPath: /config
        args:
        - --config
        - /config/curator.yaml
      volumes:
      - name: config-volume
        configMap:
          name: curator

What I notice - after a sucessful deployment procedure config map ‘curator’ disappear from the list.

kubernetes kubectl get cm -n kube-system
NAME                                 DATA   AGE
curator                          2      28s
➜  kubernetes kubectl get cm -n kube-system
NAME                                 DATA   AGE

Ofc - /config/curator.yaml file is stored correctly in my pod - works fine.
Is there any place in the documentation where I can find a description of this behavior. It is correct that ConfigMap kind disappears from the list? I think is work as design, but my question is why this solution?