Cannot get HelmChartConfig to override traefik settings

[dprothero]

I am following this documentation to create a /var/lib/rancher/k3s/server/manifests/traefik-config.yaml to override the values for the Traefik addon. I used the example YAML from the doc and, after saving the file, it seemed to work. I ran the following command:

helm -n kube-system get values traefik

And it showed the updated values for the image tag and the forwardedHeaders. Then I tried the following for my file:

apiVersion: helm.cattle.io/v1
kind: HelmChartConfig
metadata:
  name: traefik
  namespace: kube-system
spec:
  valuesContent: |-
    ports:
      web:
        redirectTo: websecure

That didn't work. In fact, running helm -n kube-system get values traefik still showed the previous values with the old 2.9.10 tag!

Then, I deleted the /var/lib/rancher/k3s/server/manifests/traefik-config.yaml file, looked at the values again, and they still hadn't changed from the original customization.

Finally, I restarted k3s using systemctl and still, the original customized values are in place!

As a noob, there's clearly something going on here that I don't understand, but strictly from my noob's lens through the documentation, something seems broken.

Is this a documentation issue (and, if so, what essential piece of information about the behavior of this system is it missing), or is there truly a problem with how this addon customization setup works?

[brandond]

Have you checked the k3s log in journald for errors applying your manifests? I suspect there's a typo in one of them and it is not valid YAML.

[dprothero]

Good suggestion. I will try to figure out how to do that.

[dprothero]

So, yes, I was able to see that it was in a crash loop with one of the helm containers for traefik and when I looked at the logs for that pod, I saw an issue:

Error: UPGRADE FAILED: execution error at (traefik/templates/_podtemplate.tpl:567:19): ERROR: Syntax of `ports.web.redirectTo` has changed to `ports.web.redirectTo.port`. Details in PR #934.

However, that doesn't answer the question of why deleting the yaml file didn't reset the configuration back to the default.

[dprothero]

Fixing the syntax error worked. Perhaps deleting the file left things in the "unclean" state and providing a valid config was the only way forward?