-
Notifications
You must be signed in to change notification settings - Fork 14
Unable to reconcile if CR contains the same extra file ConfigMap or Secret with different keys #188
Comments
Not sure I understand what exactly proposed but it seems it is covered by #179 As stated in 179, we likely should NOT require Key and mount with SubPath at all. |
Yes, I think #179 would solve this if ConfigMaps/Secrets are mounted as a whole. We would just need to handle the case where two different extra-files Resources have the same name, e.g. Meanwhile, I guess this can be reported as a bug as it prevents creating the Backstage instance correctly. This is especially annoying because, since #153 (and #160), we allow mounting extra-file Secrets by key only. The operator fails with the following error:
/kind bug Workaround for the user is to specify one extra file ConfigMap or Secret for each key. |
I think a configuration like this:
is rather confusing. In general, I can not get why one need to create a CM/Secret with unused keys?
But if we REALLY need support it I'd prefer something like:
|
I think ability to support one or all keys (we have now) is enough, picking several looks like overkill. |
As part of the migration from janus-idp to redhat-developer in https://issues.redhat.com/browse/RHIDP-1021, this will be tracked in https://issues.redhat.com/browse/RHIDP-1214 |
Currently, mounting extra files with a configmap or secret is done by providing a key. However, for a given configmap or secret, only one key can be used. The following configuration will fail because the configmap or secret name is used as the mount name so the same configmap or secret can not be used for multiple keys. This issue is to extend the operator to support such configuration.
The text was updated successfully, but these errors were encountered: