Skip to content

Adding new Kata naming convention to 2025-09-02preview API. #38067

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.

Sign up for GitHub

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

Merged
FumingZhang merged 1 commit into from
Oct 13, 2025
Merged

Adding new Kata naming convention to 2025-09-02preview API. #38067

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions ...ce-manager/Microsoft.ContainerService/aks/preview/2025-09-02-preview/managedClusters.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
{

Check notice on line 1 in specification/containerservice/resource-manager/Microsoft.ContainerService/aks/preview/2025-09-02-preview/managedClusters.json

View workflow job for this annotation

GitHub Actions / TypeSpec Requirement 

Your service description will soon be required to convert from OpenAPI to TypeSpec. See https://aka.ms/azsdk/typespec.
"swagger": "2.0",
"info": {
"title": "ContainerServiceClient",
Expand Down Expand Up @@ -9593,7 +9593,8 @@
"enum": [
"OCIContainer",
"WasmWasi",
"KataMshvVmIsolation"
"KataMshvVmIsolation",
Copy link
Member

@FumingZhang FumingZhang Oct 11, 2025

Choose a reason for hiding this comment

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

  1. want to confirm that both enums are supported by the preview API version.
  2. it’s acceptable to make breaking changes in the preview API version and KataVmIsolation is now the preferred name, you can remove support for the previous naming.

Copy link
Member

@FumingZhang FumingZhang Oct 13, 2025

Choose a reason for hiding this comment

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

  1. Yes both are still supported in the preview API version: https://msazure.visualstudio.com/CloudNativeCompute/_git/aks-rp?path=/resourceprovider/server/microsoft.com/containerservice/datamodel/v20250902preview/types.go&version=GBmaster&line=1479&lineEnd=1482&lineStartColumn=1&lineEndColumn=53&lineStyle=plain&_a=contents
  2. Yeah I know we can make breaking changes, but we're giving customers some time to switch to the new naming convention before we officially remove the old one. We also want to leave it open for now to allow everything to transition smoothly and after the GA goes smoothly we can start to remove the old naming convention. The old naming convention also only exists in preview and all customers have already been told to start switching, and the new naming convention only exists in non-preview cli.

reply from feature owner

"KataVmIsolation"
],
"x-ms-enum": {
"name": "WorkloadRuntime",
Expand All @@ -9609,7 +9610,11 @@
},
{
"value": "KataMshvVmIsolation",
"description": "Nodes can use (Kata + Cloud Hypervisor + Hyper-V) to enable Nested VM-based pods (Preview). Due to the use Hyper-V, AKS node OS itself is a nested VM (the root OS) of Hyper-V. Thus it can only be used with VM series that support Nested Virtualization such as Dv3 series."
"description": "Nodes can use (Kata + Cloud Hypervisor + Hyper-V) to enable Nested VM-based pods (Preview). Due to the use Hyper-V, AKS node OS itself is a nested VM (the root OS) of Hyper-V. Thus it can only be used with VM series that support Nested Virtualization such as Dv3 series. This naming convention will be deprecated in future releases in favor of KataVmIsolation."
},
{
"value": "KataVmIsolation",
"description": "Nodes can use (Kata + Cloud Hypervisor + Hyper-V) to enable Nested VM-based pods. Due to the use Hyper-V, AKS node OS itself is a nested VM (the root OS) of Hyper-V. Thus it can only be used with VM series that support Nested Virtualization such as Dv3 series."
}
]
},
Expand Down
Loading