When you deploy the “vSphere with Tanzu” Supervisor cluster, three nodes get created as shown in the following picture.
Now, you have to identify the leader node among them. So, how to find that out?
There may be multiple different ways to find out the leader node and in this post, I will talk about two simple ways.
Method #1 – Using vCenter console
– Login to vCenter with administrative credentials
– Click on the supervisor control plane VM’s and see the IP address detail.
– As you can see in the above screenshot, there are multiple IP addresses assigned on these nodes. Just click on that and note down the assigned ip addresses.
– Do the same with the other two supervisor control plan VM’s as well.
– You will notice that, out of three VM’s, one of them got one additional IP address and that is assigned as a virtual IP. That’s the node acting as a leader node among three supervisor control plane VM’s.
Method #2 – Using SSH access
In this method, I will talk about the different ways to find a leader node. There may be a scenario, where you are not allowed to view the detail of those nodes via vCenter console.
– Find the root password of the supervisor control plane VM. If you are looking for help on this, refer my other blog post “https://mappslearning.com/2021/12/01/ssh-login-into-vsphere-with-tanzu-supervisor-cluster-nodes/”
– Login to supervisor control plane nodes via putty. User is root and the password is the same for all the nodes.
– Run the below command on all the nodes and observe the output from each node
ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 --------------- inet 192.168.1.144/27 brd 192.168.1.159 scope global eth0 valid_lft forever preferred_lft forever inet 192.168.1.141/32 scope global eth0 valid_lft forever preferred_lft forever ----------------------- valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 inet 192.168.0.2/28 brd 192.168.0.15 scope global eth1 valid_lft forever preferred_lft forever valid_lft forever preferred_lft forever
– You will find that on one of the nodes, there is an additional IP address assigned for the eth0 interface and that’s your leader node.