I second that. Still trying to figure out the issue. It's not only SiteURL that doesn't work, other properties such as SiteName won't work either. The /mattermost/config directory is also empty

thanks for the catch.
the readme needs to be updated.

Are you willing to open a PR and make this change? thanks!

Sure, I just would like to confirm that one should define values.yaml like so (looks quite unreadable but perhaps it's expected?) How are you using it internally after these changes? I'd also add updated entries in ci/example-values.yaml.

[...]

image:
  repository: mattermost/mattermost-team-edition
  tag: 5.39.0
  imagePullPolicy: IfNotPresent

[...]

config:
  MM_SERVICESETTINGS_SITEURL: "https://chat.acme.dev"
  MM_SERVICESETTINGS_ENABLEAPIUSERDELETION: "true"
  MM_TEAMSETTINGS_RESTRICTCREATIONTODOMAINS: "acme.dev"

@mike-code this is the pattern to have environment variables for the config, this looks correct

this is injected in the Pod when it started

@cpanato Do I understand correctly that using environment variables is now the only way to set anything that was previously configured like this

configJSON:
  ServiceSettings:
    SiteURL: "https://mattermost.example.com"
  TeamSettings:
    SiteName: "Mattermost on Example.com"

And that the mattermost/config folder inside the pod is now supposed to be empty?

This format does not work for booleans with the helm template.

config:
MM_SERVICESETTINGS_ENABLEAPIUSERDELETION: "true"

The issue is that the /templates/secret-config.yaml cycles through all the values under config: and tries to convert the values to base64 encode. Which means you can't use boolean values. But if you use a string like "true" then mattermost balks on boot as it is expecting a boolean rather than a string.