Passing communications config as a k8s secret using existingSecret

[ebrianne]

ISSUE TYPE

• Feature Pull Request

SUMMARY

I have implemented in the helm chart the possibility to pass the communication config as a k8s secret and configure in the value files via an existingSecret. It can be configured in the values file via these:

communications:
    existingSecret: false
    existingSecretName: ""

Fixes #319 #211 #226 #233

[bhavin192]

Thank you for creating the change, this looks good to me. I have suggested a change related to name of the secret.

[pierluigilenoci]

@ebrianne could you please implement the suggestion in your PR?

[ebrianne]

I will implemented the changes as soon as I have time... today won't be possible. I ll try over the week end.

[pierluigilenoci]

@ebrianne any news?

[ebrianne]

I have just pushed the suggested changes

[pierluigilenoci]

@bhavin192 could you please take a look?

[pierluigilenoci]

@PrasadG193 could you please take a look?

[pierluigilenoci]

@ebrianne now it's your turn 😜

[pierluigilenoci]

😆

[bhavin192]

🎉 🚀

[onedr0p]

Please push a new release of the chart this is very much needed 🙏🏼

[rhummelmose]

Why isn't a Helm chart with this released yet?

[pierluigilenoci]

@rhummelmose nope. 😢

[pierluigilenoci]

@bhavin192 @PrasadG193 can you help to make a release?

[PrasadG193]

Hey @pierluigilenoci, I am already working on it. We will make a release this week. Sorry for the delay.

[rhummelmose]

Thanks, really need this (y)

[onedr0p]

@PrasadG193 could you please also make the GHCR image the default in the chart <3

#498

[rhummelmose]

@PrasadG193 Is this coming? :)

[onedr0p]

What's holding up the release, do you all need help on anything?

[Israphel]

How do I use this? what's the format of the secret to create?