Skip to content

[Feature] Enable the addition of Windows node pools after migrating from Kubenet to Azure CNI #4489

Closed

Description

Is your feature request related to a problem? Please describe.

The current implementation does not support Windows node pools when using Kubenet networking in Azure Kubernetes Service (AKS). However, AKS provides support for migrating from Kubenet to Azure CNI, which does support Windows node pools.

Despite completing the migration from Kubenet to Azure CNI, I am still unable to add a Windows node pool. The Windows profile remains set to null even after the migration. This limitation prevents the seamless addition of Windows node pools post-migration.

Describe the solution you'd like

Desired Enhancement
It would be highly beneficial if the Windows profile could be automatically set during the migration from Kubenet to Azure CNI. Alternatively, introducing flags or options to enable this configuration during the migration process would significantly improve the user experience and streamline the process of adding Windows node pools after migration.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
post-migration:

Failed to add node pool
Failed to add node pool 'winnp' to Kubernetes service 'featurerequest'. Error: Windows profile definition is missing for the cluster.

Activity

  1. microsoft-github-policy-service commented on Feb 17, 2025

    @microsoft-github-policy-service
    Contributor
  2. microsoft-github-policy-service commented on Mar 3, 2025

    @microsoft-github-policy-service
    Contributor

    Issue needing attention of @Azure/aks-leads

  3. microsoft-github-policy-service commented on Mar 3, 2025

    @microsoft-github-policy-service
    Contributor
  4. prdev89 commented on Mar 10, 2025

    @prdev89

    Hi, We've similar issue. Clusters migrated from Kubenet to Azure CNI Overlay would not be able to have windows nodepool as the windows_profile is missing.

    Could this feature be considered for implementation?

  5. microsoft-github-policy-service commented on Sep 7, 2025

    @microsoft-github-policy-service
    Contributor

    This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs within 7 days of this comment. Taylor Brown (@thecloudtaylor), Ally Ford (@allyford)

  6. microsoft-github-policy-service commented on Sep 14, 2025

    @microsoft-github-policy-service
    Contributor

    This issue will now be closed because it hasn't had any activity for 7 days after stale. Saber MHEDHBI (@mhedhbisaber) feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions