Create ConfigMaps automatically from existing docker-compose volume mounts.

[eldondevat]

What would you like to be added?

ConfigMaps can be created and mounted into pods where docker-compose mounts config files local to the host into containers.

Why is this needed?

I recently ran kompose to convert the docker-compose file from (/fleetdm/fleet) to something I could run on k3s. Several of the containers are configured via single-file mounts from the source directory of fleet into the accessory containers. While some (such as the docker socket) don't make sense, many are static configuration files (certificates, etc), which could make sense as ConfigMap contents.

[wzrdtales]

yeah also just wondered about this. Host files should converted to configmaps straight forward

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale