darkweaver87
commented
1 month ago Hello @srcreigh ,
Thanks for reaching out.
First, I tried to extract the chart from k3s v1.29.1+k3s2:
mkdir /tmp/charts && cd /tmp/charts
git clone git@github.com:k3s-io/k3s.git --depth 1 --branch v1.29.1+k3s2 .
cat <<EOF > test.go
package main
import "github.com/k3s-io/k3s/pkg/static"
func main(){
static.Stage("/tmp")
}
EOF
go run test.go
tar xfvz /tmp/charts/traefik-25.0.2+up25.0.0.tgz
curl -L https://github.com/traefik/traefik-helm-chart/archive/refs/tags/v25.0.0.tar.gz -o v25.0.0.tar.gz
tar xfvz v25.0.0.tar.gz
diff -rq traefik-helm-chart-25.0.0/traefik/ traefik/Files traefik-helm-chart-25.0.0/traefik/Chart.yaml and traefik/Chart.yaml differ
Only in traefik-helm-chart-25.0.0/traefik/: crds
Only in traefik/: EXAMPLES.md
Only in traefik/: LICENSE
Only in traefik/: README.md
Files traefik-helm-chart-25.0.0/traefik/templates/_helpers.tpl and traefik/templates/_helpers.tpl differ
Files traefik-helm-chart-25.0.0/traefik/templates/_podtemplate.tpl and traefik/templates/_podtemplate.tpl differ
Only in traefik/templates: validate-install-crd.yaml
Only in traefik-helm-chart-25.0.0/traefik/: tests
Files traefik-helm-chart-25.0.0/traefik/values.yaml and traefik/values.yaml differThis looks like a modified version of the one we are releasing (and I don't know why since we can override parameters which are changed by running --set at the install/upgrade stage), so I strongly encourage you to use --disable=traefik k3s option and use upstream chart :-)
You'll benefit from an up to date traefik and docs :-)
That's said, it seems you were looking at latest v29.0.1 values.yaml which differs from v25.0.0 especially in ports exposition which were refactored in v27.0.0 (cf. release note).
Do you think we can improve the doc or it's the change between v25.0.0 and v29.0.1 you didn't notice ?
Rémi
srcreigh
Welcome!
What version of the Traefik's Helm Chart are you using?
traefik-25.0.2_up25.0.0
What version of Traefik are you using?
2.10.5
What did you do?
after reading values.yaml, I tried to setup a UDP ingress route for a DNS server via the helm chart by applying this config
What did you see instead?
First thing was that dig google.com @$CLUSTER_IP was unreachable.
Traefik access logs didn't show any UDP access attempts, but i later found that traefik access logs doesn't support UDP traffic anyways.
Next I found the helm chart pod was failing.
Looking at the logs for the failing pod it had to do with the exposed.default (see end)
What is your environment & configuration?
k3s 1.29.1+k3s2-1
Tailwind
Additional Information
I ended up just sort of guessing upon a working helm chart config
I'm posting this report to request some better documentation about the values. I was able to get this to work only because of lucky guesswork.
The link to the values (which are the only docs for configuring this chart AFAICT) are buried in the 2-3rd page of README under deployment section.
The
expose: trueoption that I chanced upon which works doesn't seem to be documented at all (at least not reachable from README), and the expose.default: true option which is documented errors out.