Скачать или смотреть How to Fix Azure UI Showing Incorrect Node Count in Kubernetes Cluster?

Discover the solution to syncing your Azure UI with Kubernetes node count after manually deleting nodes. Learn simple steps to update your Azure configuration effectively.
---
This video is based on the question https://stackoverflow.com/q/66889586/ asked by the user 'Manuel' ( https://stackoverflow.com/u/14653659/ ) and on the answer https://stackoverflow.com/a/66899823/ provided by the user 'Charles Xu' ( https://stackoverflow.com/u/9773937/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Azure Ui shows wrong amount of nodes after deleting nodes with kubectl

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the Discrepancy in Node Count between Azure UI and Kubernetes

If you've been managing Kubernetes on Azure, you might have faced a situation where the Azure UI displays an incorrect number of nodes compared to what you see with kubectl. This often happens after manually deleting nodes from your Kubernetes cluster. While the Kubernetes cluster continues to function normally, the Azure interface can show a count that doesn't match the reality on the command line. Let's explore the causes of this issue and how to resolve it effectively.

The Problem

When you manually remove nodes from your Kubernetes cluster using the command kubectl drain followed by kubectl delete, it doesn't automatically notify Azure of these changes. As a result, Azure may continue to show nodes that are no longer actively part of your Kubernetes environment. For instance, if you configure your Kubernetes cluster to have 9 nodes, but kubectl get nodes only shows 7, you find yourself in a confusing situation.

Key Points to Remember

Manual Deletion: Using kubectl delete does not remove the underlying virtual machine from the Azure infrastructure.

Azure UI Mismatch: The Azure portal does not get updated automatically unless you explicitly tell it about the changes.

Unsolved Scaling: Attempts to scale up or down the node count do not rectify the discrepancy due to the stale information in the Azure UI.

How to Solve the Problem

If you're grappling with the node count mismatch, don’t worry—there are straightforward steps you can take to synchronize the Azure UI with your Kubernetes cluster.

1. Restoring Deleted Nodes to the Agent Pool

If you wish to reintegrate a node back into the Kubernetes agent pool, follow these steps:

Restart the Kubelet Service: To do this, you can use Azure's VMSS (Virtual Machine Scale Set) commands. For example, if your node instance ID is 4, you would run:

[[See Video to Reveal this Text or Code Snippet]]

This command restarts the kubelet service on the specified node, effectively directing Azure to recognize it again as part of the cluster.

2. Updating Azure with the Node Changes

If you have removed nodes entirely and need to inform Azure about the deletions, you can scale the node pool using the Azure CLI. Here is how to do it:

Scale the Node Pool: Use the following command to update the node count in Azure:

[[See Video to Reveal this Text or Code Snippet]]

This command explicitly sets the number of nodes in the given node pool to the intended count, eliminating discrepancies in Azure’s UI.

Conclusion

Working with Kubernetes clusters on Azure requires a solid understanding of not just Kubernetes commands but also how Azure interprets these changes. When you delete nodes manually using kubectl, ensure to follow up with the appropriate commands to keep Azure in the loop. By restarting kubelet services for reintegration or scaling node pools for deletions, you can maintain harmony between your Azure UI and actual Kubernetes cluster status.

If you encounter similar situations in the future, remember these straightforward steps to resolve node count discrepancies efficiently. Happy clustering!