fix: Enable Extra Env in Chart

[3schwartz]

Related Tickets & Documents

In PR #487, support was added to provide additional environment variables to the operator.

However, it is currently not possible to specify these variables via the Helm Chart.

Changes

This PR enables the ability to provide extra environment variables to the operator from the Helm Chart.

[coveralls]

Pull Request Test Coverage Report for Build 12360249215

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 97.214%

---

Totals
Change from base Build 12359248301:	0.0%
Covered Lines:	1021
Relevant Lines:	1036

---

💛 - Coveralls

[3schwartz]

Hi @ekampf

I realized that in PR #487, I forgot to make the new settings configurable through the Helm chart.
Would you be able to review this?

Should I also bump the chart version as part of this change?

[ekampf]

@3schwartz yeah missed that too...
yes Please up the chart version and I'll release another version

[3schwartz]

@3schwartz yeah missed that too... yes Please up the chart version and I'll release another version

@ekampf Done

One of the integration tests is failing with the error remote_network_id missing, but I’m not sure why my changes would cause this 🤔

The chart is currently referencing the latest image. Once this PR is merged, will both the new chart and the updated image be available with the changes from the prior PR, or is a release action required?

[ekampf]

Do we want to do that or just keep the k8s structure (name, value) and do something like {{- toYaml .Values.extraEnvVars | nindent 8 }} ?

[ekampf]

I'm looking at whats common in other charts and it seems most do something like:

## extraEnvVars:
##   - name: FOO
##     value: "bar"

[ekampf]

@3schwartz closing this in favor of #491