Skip to content

fix: in case of azure cni overlay use correct options to match RP#8609

Merged
awesomenix merged 1 commit into
mainfrom
nishchay/azurecni/fix
May 29, 2026
Merged

fix: in case of azure cni overlay use correct options to match RP#8609
awesomenix merged 1 commit into
mainfrom
nishchay/azurecni/fix

Conversation

@awesomenix
Copy link
Copy Markdown
Contributor

fix azure cni with overlay

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes the Test_Ubuntu2204_AzureCNI e2e scenario so that the node bootstrapping configuration matches how the AKS RP actually configures nodes for an Azure CNI Overlay cluster. With overlay, the RP sets NetworkPlugin=none on the node and applies two well-known labels (podnetwork-type=overlay and nodenetwork-vnetguid=<vnet GUID>) so the in-cluster Azure CNI overlay components configure the node correctly. To support this, the Cluster struct now also surfaces the VNet's resourceGUID.

Changes:

  • Switch the overlay scenario's NBC mutator to NetworkPluginNone and add the two overlay-specific node labels.
  • Extend VNet and Cluster with resourceGUID / VNetResourceGUID and populate it from getClusterVNet.
  • Fetch the VNet in prepareCluster (in parallel via dag.Go) so the GUID is available to all scenarios.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
e2e/scenario_test.go Reconfigure Test_Ubuntu2204_AzureCNI overlay scenario: NetworkPlugin=none plus overlay/VNet-GUID node labels.
e2e/cluster.go Add VNetResourceGUID to Cluster, plumb it through prepareCluster, and read ResourceGUID from the AKS VNet in getClusterVNet.

@awesomenix awesomenix merged commit 38f52b5 into main May 29, 2026
28 of 31 checks passed
@awesomenix awesomenix deleted the nishchay/azurecni/fix branch May 29, 2026 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants