chart forces svc.cluster.local in service names

[deefdragon]

I have deployed my cluster with a custom domain. This results in svc.example.com as my root for all of my services, meaning that the current default deployed cluster, which uses svc.cluster.local can not boot the api pods.

[dabeeeenster]

Can you provide more details as well as your values file?

[deefdragon]

"api":
  "livenessProbe":
    "timeoutSeconds": 4
"ingress":
  "api":
    "enabled": true
    "hosts":
    - "host": "flags.example.com"
      "paths":
      - "/"
  "frontend":
    "enabled": true
    "hosts":
    - "flagsmith.example.com"

The issue is that the env value in the deployment generated for the influx connection, INFLUXDB_URL has a hardcoded domain ending. Its obviously not the only var to have this problem, just the one I encountered first.

This should be solvable by adding a config option to the values to override svc.cluster.local with some other dns value. I am unsure if this way that other charts do this however, and what the normal method for dealing with this situation is. I suspect bitnami has had to deal with this exact issue previously, so Id reference them.

[dabeeeenster]

OK will take a look cc @khvn26 !