Use projected volumes for automount configmaps/secrets when they use the same mount path #1021
Labels
new¬eworthy
For new and/or noteworthy issues
sprint/current
Is assigned to issues which are planned to work on in the current team sprint
Milestone
Description
Currently, attempting to start a workspace in a namespace with automount configmaps/secrets that share the same mountpath results in the workspace failing to start, with message like
Instead, DWO could mount both configmaps using a projected volume.
Additional context
The text was updated successfully, but these errors were encountered: