Config maps don't apply when using a differen OS base image

[likeMyCoffee]

Issue submitter TODO list

• I've looked up my issue in FAQ
• I've searched for an already existing issues here (legacy) and here
• I've tried installing latest charts and the issue still persists there
• I'm running a supported version of the application & chart which is listed here

Describe the bug (actual behavior)

( I've supplied the solution below but filling in the form :-) )

I'm running a debian based zulu-openjdk-17 OS version because Alpine doesn't do DNS in Kubernetes.

When trying to use the inline-configmaps or configmaps for the config I'm unable to. It no longer works for me. However everything works as expected when using the environment variables.

Expected behavior

Config to apply

Your installation details

I'm runing kafka ui 0.7.2
I'm running helm chart 0.7.6
Application config irrelevant becasue it's not applying. I've provided the fix and then my config applies and works.

Steps to reproduce

Install with helm chart and then use the yamlApplicationConfig or yamlApplicationConfigConfig

Screenshots

Not applicable

Logs

Not applicable

Additional context

The solution:

In deployment.yaml
Change

         - name: SPRING_CONFIG_ADDITIONAL-LOCATION

To

        - name: SPRING_CONFIG_ADDITIONALLOCATION

Reasoning:
Environment variable support for a dash (-) is dropped in bash. So mappings should not have a dash. In your documentation you point to a tool that does the correct mapping, however you didn't do it in the helm chart.
I believe Alpine Linux doesn't use bash so it's masking the bug and that's why it's probably working for everyone but me :)