docs: update service CIDR documentation for Kubernetes 1.33 GA extension#413
Open
tdihp wants to merge 1 commit intoMicrosoftDocs:mainfrom
Open
docs: update service CIDR documentation for Kubernetes 1.33 GA extension#413tdihp wants to merge 1 commit intoMicrosoftDocs:mainfrom
tdihp wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
…ion support Update five networking articles to reflect that service IP ranges can now be extended after cluster creation on Kubernetes 1.33+ clusters using the ServiceCIDR resource (GA since K8s 1.33, MultiCIDRServiceAllocator feature gate enabled by default). Updated articles: - concepts-network-legacy-cni.md - configure-kubenet.md - concepts-network-ip-address-planning.md - concepts-network-azure-cni-overlay.md - use-byo-cni.md Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Ping He <pihe@microsoft.com>
Contributor
|
@tdihp : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Contributor
|
Learn Build status updates of commit 57b3361: ✅ Validation status: passed
For more details, please refer to the build report. |
tdihp
changed the title
Contributor
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates AKS networking documentation to reflect that, starting with Kubernetes 1.33, clusters can extend the Kubernetes service IP range after creation via the upstream ServiceCIDR resource.
Changes:
- Added Kubernetes 1.33 guidance (notes/wording) pointing to the upstream
ServiceCIDR/ “Extend Service IP Ranges” documentation. - Updated
ms.datemetadata across the touched articles. - Added
ai-usage: ai-assistedfront matter to the updated articles.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| articles/aks/use-byo-cni.md | Adds a note that service IP ranges can be extended post-create on Kubernetes 1.33+ via ServiceCIDR; updates front matter. |
| articles/aks/configure-kubenet.md | Updates prerequisite guidance to mention the Kubernetes 1.33+ service range extension capability; updates front matter. |
| articles/aks/concepts-network-legacy-cni.md | Replaces “can’t be updated” wording with Kubernetes 1.33+ ServiceCIDR note + pre-1.33 limitation; updates front matter. |
| articles/aks/concepts-network-ip-address-planning.md | Adds Kubernetes 1.33+ mention in the service address range row; updates front matter. |
| articles/aks/concepts-network-azure-cni-overlay.md | Adds a Kubernetes 1.33+ note under service address range; updates front matter. |
| * The virtual network for the AKS cluster must allow outbound internet connectivity. | ||
| * Don't create more than one AKS cluster in the same subnet. | ||
| * AKS clusters can't use `169.254.0.0/16`, `172.30.0.0/16`, `172.31.0.0/16`, or `192.0.2.0/24` for the Kubernetes service address range, pod address range, or cluster virtual network address range. The range can't be updated after you create your cluster. | ||
| * AKS clusters can't use `169.254.0.0/16`, `172.30.0.0/16`, `172.31.0.0/16`, or `192.0.2.0/24` for the Kubernetes service address range, pod address range, or cluster virtual network address range. On clusters running Kubernetes versions earlier than 1.33, these ranges can't be updated after you create your cluster. Starting with Kubernetes 1.33, you can extend the service IP range after cluster creation using the [`ServiceCIDR`](https://kubernetes.io/docs/tasks/network/extend-service-ip-ranges/) Kubernetes resource. |
There was a problem hiding this comment.
This bullet reads as if all of the listed ranges (service CIDR, pod CIDR, and VNet CIDR) become updatable on Kubernetes 1.33+. In Kubernetes 1.33, only the service IP range can be extended (via ServiceCIDR); the pod address range and virtual network address range still can’t be changed after cluster creation. Please reword to explicitly scope the “extend after cluster creation” statement to the service address range only (and keep the immutability statement for pod/VNet ranges).
Suggested change
| * AKS clusters can't use `169.254.0.0/16`, `172.30.0.0/16`, `172.31.0.0/16`, or `192.0.2.0/24` for the Kubernetes service address range, pod address range, or cluster virtual network address range. On clusters running Kubernetes versions earlier than 1.33, these ranges can't be updated after you create your cluster. Starting with Kubernetes 1.33, you can extend the service IP range after cluster creation using the [`ServiceCIDR`](https://kubernetes.io/docs/tasks/network/extend-service-ip-ranges/) Kubernetes resource. | |
| * AKS clusters can't use `169.254.0.0/16`, `172.30.0.0/16`, `172.31.0.0/16`, or `192.0.2.0/24` for the Kubernetes service address range, pod address range, or cluster virtual network address range. The pod address range and cluster virtual network address range can't be updated after you create your cluster. The Kubernetes service address range also can't be updated after cluster creation on clusters running Kubernetes versions earlier than 1.33. Starting with Kubernetes 1.33, you can extend only the service IP range after cluster creation by using the [`ServiceCIDR`](https://kubernetes.io/docs/tasks/network/extend-service-ip-ranges/) Kubernetes resource. |
davidsmatlak
approved these changes
Apr 17, 2026
Contributor
|
#sign-off |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update five networking articles to reflect that service IP ranges can now be extended after cluster creation on Kubernetes 1.33+ clusters using the ServiceCIDR resource (GA since K8s 1.33, MultiCIDRServiceAllocator feature gate enabled by default).
Updated articles: