Overwrite cluster.local suffix

[m4rc3l-h3]

Hi everyone,

I am trying to deploy the Helm chart on a cluster which has been configured to use xx.cluster.home instead of xx.cluster.local. That causes some issues with the creation of traefik Middleware resouces, in particular the forwardAuth.address. I could track it down to line 574 in _helpers.tpl.

I am not that familiar with Helm and was wondering if and where to set .Cluster to a custom value. Is that possible within values.yaml?

Any guidance would be much appreciated. Thank you for your support!
If that is not the right place to ask, please let me know. Thanks.

[james-d-elliott]

Can't say I've ever seen this before. I don't recall adding this. I'll take a look at it for 0.9.0 which will bundle 4.38.0. I could use some additional testers to be fair as it's a fairly major rework.

[m4rc3l-h3]

Thank you for your swift response. Sure I can and will test it.
As far as I can see in the current version of files in the repo, it is the only place where it is used. In addition, it is also the only place where it causes issues in my current deployment as other components (e.g., mysql, redis) allow to specify the hostname directly. However, I will have a closer look and do some more testing and add findings to this thread, if that is okay?

Maybe an idea would be to add clusterDomain to values.yaml and use that in the helper.tpl? This is, for example, done by some bitnami charts I am using: mongodb, postgresql?

I could give it a try, if that is okay and you could provide some guidance.

Thank you again for your feedback, much appreciated.

[james-d-elliott]

Available in a802da8, see #215

[m4rc3l-h3]

Hi @james-d-elliott
Sorry for the late reply and thank you again for looking into it/adding the option. I am currently testing 0.9.0-beta5 and the kubeDNSDomainOverride worked for the use case described above. Still working on the complete setup, but thank you very much for your support.