If you're using Azure API Management (APIM) services, you've likely seen this message: "Support for the single-tenant v1 (STv1) platform ends on 8/31/24. Migrate instances before that date to the new platform version (STv2) for continued support and access to new features." This announcement highlights the urgency of migrating to STv2. To ensure a smooth transition, it's crucial to analyze our architecture, understand technical constraints, explore possible approaches, and assess risks. Here’s a summarized guide on how I managed the migration using the VNET-injection method. My Case: APIM with Dedicated Public IP and Subnet Configuration: APIM with a dedicated public IP and a dedicated subnet. Assigned private IP with NAT in a controlled VNET. Need to maintain IP addresses and DNS. Issues: APIM migration requires a new public IP, new subnet with private IP, new DNS, and new NSG. APIM instances acquire IP addresses randomly, complicating existing firewall rules, NS...
I've upgraded my AKS nodes in Cluster last night. After upgraded both nodes, all my apps went down and all my internal load balancers was not able to access. Spending many hours in troubleshooting and ends up with the miserable findings of root caused. That's it.... The Resource Tagging used in my Cluster and it's resource has exceed more than 50 tags. Microsoft recommendation is to maintain the tags less than 20. After I've removed over 30 tags and refresh the nodes then only all my resources are back up online as well as the applications. Currently, the resource sync the tags with cluster are below, AKS Cluster itself Router Table Pubic IP Load Balancer Network Security Group Virtual Network AKS managed kubelet msi AKS managed addon msi Private DNS zone Private endpoint So, beware this when you have more than 50 tags on your AKS Cluster. Cheer! Have a good day. (Be knowledgeable, pass it on then)