Azure / Azure/AKS

Missing NodeNetworkConfigs & OverlayExtensionConfigs CRDs causes node creation failure in AKS v1.33.0

Open
#5,473 8 comments 0 reactions 2 assignees Assigned to @neaggarwMS View on GitHub
advanced-container-networking-services control-plane feature-request networking/azcni
Dominant language
TypeScript
Stars
2.1k
Forks
395
Avg merge
2d 22h
Merged PRs (30d)
13

Description

**Description:**
While working with **AKS cluster version 1.33.0**, I encountered an issue related to CRDs required for networking.

When creating an AKS cluster, the following CRDs are automatically deployed:

* `NodeNetworkConfigs` (`acn.azure.com/v1alpha`)
* `OverlayExtensionConfigs` (`acn.azure.com/v1alpha1`)

**Steps to reproduce:**

1. Create an AKS cluster (v1.33.0).
2. Delete the `NodeNetworkConfigs` and `OverlayExtensionConfigs` CRDs.
3. Attempt to **add a new node** to the cluster or do something that ends up creating the new node

**Observed behavior:**

* Node creation fails because the required CRDs are missing.

**Expected behavior:**

* There should be a **reconciliation mechanism** to automatically recreate these essential CRDs if they are deleted, preventing node/network failures.

**Environment:**

* AKS version: 1.33.0
* Cloud provider: Azure
* Cluster type: Test/Development

**Additional context:**

* This only occurs if the CRDs are deleted.
* Suggestion: Include these CRDs in the cluster’s internal reconciliation loop to improve resiliency.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.