Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AKS Learn feedback: #64

Open
pasilvaa opened this issue Oct 15, 2024 · 1 comment
Open

AKS Learn feedback: #64

pasilvaa opened this issue Oct 15, 2024 · 1 comment
Assignees
Labels

Comments

@pasilvaa
Copy link

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

@schaffererin
Copy link
Contributor

#assign:schaffererin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants