helm - Invalid deployment config if existingSecret is specified

[Fabccc]

Issue

While using an existingSecret as configuration AND supplying a different name than mercure.fullName, "GLOBAL_OPTIONS" and "CADDY_EXTRA_CONFIG" both uses a non-existing secret (called mercure.fullName).

Workaround

Name the existingSecret with the same name in mercure.fullName or mercure.fullNameOverride

Lasting solution

Make "GLOBAL_OPTIONS" and "CADDY_EXTRA_CONFIG" reference the mercure.secretName instead of mercure.fullName.

[dunglas]

It's likely a problem introduced in https://github.com/dunglas/mercure/pull/809. Maybe @Julian-Louis as an idea of what's going on?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[yosrib]

Hello,

Any news about this issue ? I have the same one.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.