Open manojgop opened 2 months ago
ACK, thanks for the report @manojgop. This does seem to be an issue. @vthapar can provide some details.
CustomDNSCONfig was added at the time for an issue with Azure/AKS clusters where they required DNS configuration to be in a separate file and xyz.server
format. That is why we use lighthouse.server
. But rke2 expects it in the Corefile section itself. This will require some work, and potentially a new flag without breaking any existing AKS deployments.
What happened:
Submariner does not add LightHouse DNS entry in configmap "corefile" section in case of RKE2 cluster. For RKE2, I see "rke2-coredns" instead of core-dns. rke2-coredns is NOT configured to forward requests for domain clusterset.local to Lighthouse CoreDNS Server in the cluster making the query. I had to edit this config file manually in "corefile" section in all clusters to make it work.
The output of
kubectl -n kube-system describe configmap rke2-coredns-rke2-coredns
is as following. The forward rule is present inlighthouse.server
section. But that didn't work in case of RKE2.nslookup nginx.default.svc.clusterset.local returned server can't find nginx.default.svc.clusterset.local: NXDOMAIN
I had to manually edit config map and keep following section in the
corefile
section of the configmapAdding the rules in
lighthouse.server
section seems to be a issue. Looks like RKE2 is expecting the rules inCorefile
sectionWhat you expected to happen:
Lighthouse DNS to work for exported services in RKE2 clusters
How to reproduce it (as minimally and precisely as possible):
Try using submariner with RKE2 cluster and export service
Anything else we need to know?: Check Slack for more details slack comments
Environment:
subctl diagnose all
):subctl gather
):