-
Notifications
You must be signed in to change notification settings - Fork 37
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.
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
Nested VM environment #178
Comments
Yes, we want great AKS solutions in VM environments. What's your use case? |
Hi @scooley / @SummerSmith , as the original poster did not answer yet: Our use-case is relatively straight forward. We aim to deliver a product on AKSEE where more than 3/4 of customers have already expressed that they would like to virtualize the solution instead of receiving a HW device. We have confirmed, as described in AKSEE documentation, that AKSEE works on VMware/vSphere which also still seems to be the most prominent solution with the customers. |
Hi @scholz , We do support nested virtualizations on Hyper-V ( as you can already validate many of the scenarios on Azure VM, for example). Azure Arc Jumpstart scenarios are built on Azure VMs that do make use of nested virtualization on Hyper-V. |
Hi @parameshbabu , thanks for your reply and the explaination. Right now, I do not have concrete names of other virtualization products that are employed, but I will reach out to CSMs / POs to ask if they can name such concrete examples that customers are using. |
@scholz, thanks for sharing your perspective here. We have not explored another virtualization tech as we haven't seen any demand so far. |
I’m looking at the documentation here https://learn.microsoft.com/en-us/azure/aks/hybrid/aks-edge-howto-setup-nested-environment and it says that only VMware ESXi is supported for production. Is Microsoft planning to support other nested VM environment (such as Hyper-V or Nutanix) in the future roadmap? If so, when would it be available? If not, what were the rational not to support?
The text was updated successfully, but these errors were encountered: