Bridget Kromhout

@mboersma I'm looking at https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/kubeadm/2067-rename-master-label-taint/README.md#renaming-the-node-rolekubernetesiomaster-node-taint and it looks like this _may_ not be a breaking change in 1.24 for AKS Engine - can you check and let me know if...

> So I don't think there are any action items here since 1.24 works and it's the last dance for aks-engine. Thanks, @mboersma - resolving this issue.

> TODO: update docs to discourage choosing bridge mode? Done in https://github.com/Azure/aks-engine/pull/4857.

Closing per @mboersma as this is fixed and/or documented in all current, supported versions.

Thanks for the feedback. As the AKS Engine project is deprecated, we're not going to make this change; I suggest looking at [Kubernetes Cluster API Provider Azure](https://capz.sigs.k8s.io/#kubernetes-cluster-api-provider-azure) as a replacement...

Hi, @jprecuch - while there isn't a one-size-fits-all method, we can definitely add some migration steps to the AKS Engine docs to help AKS Engine users move onto AKS. Thanks!

Note: this is the AKS docs page on migration: https://docs.microsoft.com/en-us/azure/aks/aks-migration

Hi, @jprecuch - as you've probably seen, AKS migration can have specifics that are best covered by the AKS team's documentation in https://docs.microsoft.com/en-us/azure/aks/aks-migration. If you have questions that aren't answered...

@jaer-tsun Thanks for pointing this out. We are in the process of moving all tests away from using AKS Engine, because AKS Engine is deprecated as explained in the [AKS...

Hi, @jaer-tsun - closing this now because we are moving all tests away from using AKS Engine. Please see https://cloud-provider-azure.sigs.k8s.io/development/e2e/e2e-tests/ for running e2e tests using CAPZ instead - thanks.