configmaps-and-pods
explaining well enough sample about to configmap.

using-configmaps-as-files-from-a-pod
explaining spec.volumes level fields

it would be good if both are in a section

/sig doc

@tamilselvan1102: The label(s) sig/doc cannot be applied, because the repository doesn't have them.

/sig docs
/triage accepted

/assign @pegasas

Hi, all,

After seeing this issue carefully, I found this issue is not duplicate.

For configmaps-and-pods explains we can use multiple file in ONE configmap and may be mount in the near future.
For using-configmaps-as-files-from-a-pod explains how configmap are mount to pod/deployment and etc.

In fact it is on different aspects of configmap.
It is both significant in k8s yaml development.

Thanks for your assessment @pegasas, but I do not know exactly what you meant by "[...] and may be mount in the near future." Can you please elaborate on that?

I agree that it is important to demonstrate different use cases of ConfigMaps. But maybe it would be better educational to explain the ConfigMap object in the first section ConfigMaps and Pods and in the following sections under Using ConfigMaps to show more specifically how this ConfigMap object can be used in different ways. So in addition to the existing sections:

• Using ConfigMaps as files from a Pod
• Using ConfigMaps as environment variables

the following could be listed:

• Using Configmaps as commands and args
• Using ConfigMaps via the Kubernetes API

All sections could refer to the example ConfigMap listed under ConfigMaps and Pods. This would make this page clear and consistent.

Thanks for your assessment @pegasas, but I do not know exactly what you meant by "[...] and may be mount in the near future." Can you please elaborate on that?

It descripe such a scenario, which is multiple file in one configmap, like core-site.xml and hdfs-site.xml, and mount into hadoop to deploy on k8s. this is common scenario on for configmaps-and-pods.

the following could be listed:

• Using Configmaps as commands and args
• Using ConfigMaps via the Kubernetes API

This looks better, it looks like 2 examples on https://kubernetes.io/docs/concepts/configuration/configmap/#configmap-object has elaborated scenarios on

• Using ConfigMaps as files from a Pod
• Using ConfigMaps as environment variables

Maybe we can delete these 2 characters and directly refer example on https://kubernetes.io/docs/concepts/configuration/configmap/#configmap-object?

These seems close to your proposal on #45847 (comment)?