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

Bug: AKS Construction does not pass necessary parameters for CNI Overlay networking #617

Closed
pjlewisuk opened this issue Jul 12, 2023 · 4 comments · Fixed by #633
Closed
Assignees

Comments

@pjlewisuk
Copy link
Contributor

pjlewisuk commented Jul 12, 2023

Describe the bug
When you select "CNI Overlay Network" and "Custom Networking" on the "Networking Details" tab, you get to define your custom network configuration, including parameters for POD Network, Service Network and DNS Service IP under Kubernetes Networking Configuration. However, the Pod Network and Service Network parameters are not passed into the Deployment script generated by AKS Construction:

image

podCidr is missing from the deployment command:
image

To Reproduce
Steps to reproduce the behavior:

  1. Go to AKS Construction homepage
  2. Navigate to "Networking Details"
  3. Check the "CNI Overlay Networking" box under "CNI Features"
  4. Select "Custom Networking" option under "Default or Custom VNET"
  5. Enter custom values for "VNET Address space", "AKS Nodes subnet", "POD Network", "Service Network", and "DNS Service IP"
  6. Navigate to the "Bash" or "PowerShell" tabs under "Deploy Cluster", and examine the output
  7. Note missing podCidr parameter (even though networkPluginMode=Overlay is set)

Expected behavior
podCidr parameter should get passed to the deployment command so that CNI Overlay networking is set up correctly.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

@pjlewisuk
Copy link
Contributor Author

If I add the podCidr parameter to the az deployment command prior to running it, with a "Default Networking" cluster configuration, it does not take effect, even though I can see it gets passed to the deployment. I presume this is because the custom_vnet parameter is set to false, and so it gets ignored?

If I add the podCidr parameter when "Custom Networking" is used, I get the cluster configuration I expected: with nodes and pods running in separate subnets. I presume this is because custom_vnet is set to true.

@pjlewisuk pjlewisuk changed the title AKS Construction does not pass necessary parameters for CNI Overlay networking Bug: AKS Construction does not pass necessary parameters for CNI Overlay networking Jul 12, 2023
@khowling
Copy link
Contributor

@samaea pls update with IP CIDR not passed

@github-actions
Copy link
Contributor

Issue smells stale, no activity for 30 days. Stale Label will be removed if the issue is updated, otherwise closed in a month.

@github-actions github-actions bot added the stale An issue that hasn't had a lot of love recently label Aug 27, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 27, 2023
@pjlewisuk
Copy link
Contributor Author

Bump to reopen

@pjlewisuk pjlewisuk reopened this Sep 27, 2023
@github-actions github-actions bot added Keep Open and removed stale An issue that hasn't had a lot of love recently labels Sep 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants