App having ConfigMap & Secret with same name only links to Secret

[ghost]

Ask a Question!

In Portainer BE 2.28.1, I created a ConfigMap and a Secret with the same name.

Expectation: I'd expect that Portainer would render a link to the ConfigMap for those variables sourced from that map, and a link to the Secret for those variables.

Actuality: Instead, I get all the variables having a link to the Secret.

Work-around: Of course, just name the two differently, but I would expect Portainer to be smarter about this.

[Nick-Portainer]

Hi @todfox-net, thanks for raising this.

I just want to confirm—are the value references correct in terms of being sourced from the appropriate locations? but the links on the right all point to the secret, even for the config map values? Or are the values that are supposed to come from the config map also coming from the secret?

internal: FR-558

[ghost]

Hi, Nick! The values are correct, but the icon and link to the right are not correct. So it is sourcing from the configmap but providing the lock icon and link to the Secret of the same name.

[Nick-Portainer]

Great, thank you for this. I have raised this internally