Skip to main content

Unable to access Ingress Controller in Azure AKS issue

By
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)
Labels:

Comments

  1. Gokul KrishJuly 7, 2026 at 5:48 AM

    This is a fantastic overview of network virtualization and why it's essential in modern data centers. The challenges with routing, firewalls, load balancing, and VPN services are real pain points that I've encountered as well. Network virtualization truly simplifies management and scaling. As I look to advance my career, I'm also considering adding automation testing to my skill set. I came across selenium java course with placement guarantee in electronic city and it seems like a solid option for career growth. Thanks for this informative post!

    ReplyDelete

Post a Comment

Popular posts from this blog

Why do we need network virtualization?

By
We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca...
144 comments
Read more

Link Aggregating with Synology NAS and Cisco Switch

By
I’d like to share how to setup Link Aggregating between Synology NAS and Cisco Switch. I’ve got one Synology NAS with 4 Network Ports and I’m going to use 2 of them. Both Network Port to be as one Logical Link, Fault Tolerance and Load Balancing. To do that, I need to configure Link Aggregating on Synology NAS and EtherChannel with LACP on Cisco Switch. Below is brief steps to do to meet with my requirements. - Get connected Synology NAS and Cisco Switch as shown in picture. - Bonding two Network Ports of Synology NAS and assign IP Address - Configure EtherChannel with LACP in Cisco Switch and add two physical ports as Member. OK. Let’s begin from Synology NAS. - Login to the Synology and go to Control Panel>Network>Create>Create Bond - Select IEEE 802.3ad to get Fault Tolerance and Load Balancing Featureyou’re your switch not support 802.3ad you can only select Fault Tolerance only feature). After that click “Next”. - Choose the network port f...
40 comments
Read more

Fortigate guide for Begineer - 6

By
I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a...
2 comments
Read more