-
Based on the recent changes I got a simple dual-stack cluster running in a VM but discovered that the Traefik ingress still is set to only run on IPv4. I assume this was not yet updated… should I remove the default Traefik ingress and try to get this working myself or is it possible to change the Traefik deployment to utilize dual stack? |
Beta Was this translation helpful? Give feedback.
Answered by
strayer
Jan 20, 2022
Replies: 1 comment
-
In case anyone is having the same problem, this helm chart config seems to have made Traefik dual-stack aware: # /var/lib/rancher/k3s/server/manifests/traefik-config.yaml
apiVersion: helm.cattle.io/v1
kind: HelmChartConfig
metadata:
name: traefik
namespace: kube-system
spec:
valuesContent: |-
service:
spec:
ipFamilyPolicy: RequireDualStack |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
strayer
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In case anyone is having the same problem, this helm chart config seems to have made Traefik dual-stack aware: