This message was deleted.
# rke2
a
This message was deleted.
l
Ideally the helm chart can take a Value, but that's a perfect world. In the past for these I've manually just duplicated the rke2-coredns-rke2-coredns service definition with just the name changed telepresence had this issue and it took a code change to fix. https://github.com/telepresenceio/telepresence/issues/2599
p
There is an nginx revproxy that has a resolver
resolver kube-dns.kube-system.svc.cluster.local
and changing that to:
resolver rke2-coredns-rke2-coredns.kube-system.svc.cluster.local
fixes the problem, but I'm not fond of that solution…
Thanks @little-actor-95014
Copy code
apiVersion: v1
kind: Service
metadata:
  name: kube-dns
  namespace: kube-system
spec:
  internalTrafficPolicy: Cluster
  ipFamilies:
  - IPv4
  ipFamilyPolicy: SingleStack
  ports:
  - name: udp-53
    port: 53
    protocol: UDP
    targetPort: 53
  - name: tcp-53
    port: 53
    protocol: TCP
    targetPort: 53
  selector:
    app.kubernetes.io/instance: rke2-coredns
    app.kubernetes.io/name: rke2-coredns
    k8s-app: kube-dns
  type: ClusterIP
← applying this (taken from teh github) fixed it. Thanks so much for the pointer.
🙌 1