During an investigation i noticed that when using custom Service CIDR like 192.168.0.0/16 where the kube-dns service ip is 192.168.0.10 karpenter's nodepool is still defaulting the kube-dns service ip to 10.0.0.10, therefore when new pods are scheduled, it gets the IP 10.0.0.10 in the /etc/resolv.conf.
After discussing this with our PG:
it seems like Node autoprovisioning doesn't support custom Service CIDR while in preview, it would be best to change our documentation. According to the PG this will be supported in GA.
Type of issue
Missing information
Feedback
Hi Team,
During an investigation i noticed that when using custom Service CIDR like 192.168.0.0/16 where the kube-dns service ip is 192.168.0.10 karpenter's nodepool is still defaulting the kube-dns service ip to 10.0.0.10, therefore when new pods are scheduled, it gets the IP 10.0.0.10 in the /etc/resolv.conf.
After discussing this with our PG: it seems like Node autoprovisioning doesn't support custom Service CIDR while in preview, it would be best to change our documentation. According to the PG this will be supported in GA.
Page URL
https://learn.microsoft.com/en-us/azure/aks/node-autoprovision?tabs=azure-cli
Content source URL
https://github.com/MicrosoftDocs/azure-aks-docs/blob/main/articles/aks/node-autoprovision.md
Author
@schaffererin
Document Id
d269da23-8613-c13b-6fb8-601b251fd96f