Properly Enable Accelerated Networking for AvSet Clusters #101
Labels
area/performance
Performance (across all domains, such as control plane, networking, storage, etc.) related
area/quality
Output qualification (tests, checks, scans, automation in general, etc.) related
kind/enhancement
Enhancement, improvement, extension
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
platform/azure
Microsoft Azure platform/infrastructure
How to categorize this issue?
/area performance
/area quality
/kind enhancement
/priority normal
/platform azure
What would you like to be added:
Recently Accelerated Networking was enabled with #65. The decision to enable it or not was based only on the VM type and OS, but this caused troubles with AvSet clusters - basically the migration to VMs with enabled Accelerated Networking is requiring all non-enabled VMs to be deleted before new ones are created. If this is not done, VM creation is failing with
ExistingAvailabilitySetWasNotDeployedOnAcceleratedNetworkingEnabledCluster
, thus we disabled Accelerated Networking with #100 for all AvSet based shoot clusters.Once #61 is implemented, we can use AvSet per machine class which will allow us to properly enable Accelerated Networking for non-zoned clusters, again.
Why is this needed:
See #55
The text was updated successfully, but these errors were encountered: