https://rancher.com/ logo
Powered by
b

bright-fireman-42144

02/24/2023, 5:32 PM
quick question to help me troubleshoot my VIP not being reachable after a reboot. How can I determine from the command line on any host which node is currently the 'master'?
found a sneaky way to determine that: kubectl get pods -n longhorn-system -o wide | grep manager except: The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port? As this is just a lab and I've messed around by removing a node and converting that bare metal machine just so I can run rancher manager outside the cluster. I'll just rebuild everything and make sure I write down my cluster token and all the things I should have done from the beginning.
f

full-plastic-79795

02/27/2023, 1:07 PM
Copy code
harv-4:/home/rancher # kubectl get lease -n harvester-system plndr-svcs-lock -o yaml
apiVersion: <http://coordination.k8s.io/v1|coordination.k8s.io/v1>
kind: Lease
metadata:
  creationTimestamp: "2022-11-08T09:25:05Z"
  name: plndr-svcs-lock
  namespace: harvester-system
  resourceVersion: "199614353"
  uid: e756e8cc-1c4e-43f6-a773-7a9c68cfbee1
spec:
  acquireTime: "2022-11-08T09:25:05.596517Z"
  holderIdentity: harv-4
  leaseDurationSeconds: 10
  leaseTransitions: 0
  renewTime: "2023-02-27T08:15:22.205920Z"
The value of spec.holderIdentity allows you to determine which node the vip resides on
4 Views
Powered by