This message was deleted.
# harvester
a
This message was deleted.
b
maybe it's not aware of it's dns name?
s
I have been using MGMT IP since first installed. I don't have DNS name for mgmt IP.
Which pod is responsible for harvester gui ?
g
do you have a support bundle handy?
s
@great-bear-19718 How I generate support bundle from command line ? I can't get it from gui.
w
This has probably happened before, but had a network configuration change which affected the harvester cluster. None of the (3) nodes are showing a management URL, and each of them are only showing their own IP address in
ip addr show mgmt-br
. kubectl also fails on each node with 127.0.0.1 fail tcp
I've recovered the network configuration, but is the cluster dead at this point?
Or can I manually re-assign a VIP node
I did find one of the nodes has this in the harvester.config
Copy code
install:
  mode: create
vip: xxx.xxx.xxx.xxx
would that be the VIP? can I safely reboot that one?
s
I checked 5 nodes and none of them have the VIP IP, however the VIP IP forwards to harvester .
The VIP IP shown in kubectl get svc.
Copy code
k get svc -n kube-system
NAME                                      TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)                      AGE
harvester-snapshot-validation-webhook     ClusterIP      10.53.34.249    <none>          443/TCP                      42d
ingress-expose                            LoadBalancer   10.53.105.70    10.96.117.109   443:32594/TCP,80:32434/TCP   42d
rke2-coredns-rke2-coredns                 ClusterIP      10.53.0.10      <none>          53/UDP,53/TCP                42d
rke2-ingress-nginx-controller-admission   ClusterIP      10.53.130.181   <none>          443/TCP                      42d
rke2-metrics-server                       ClusterIP      10.53.228.196   <none>          443/TCP                      42d
w
ah crap, I didn't mean for my posts to go into this thread, my apologies @sparse-ghost-91718!
s
np.
I rebooted the 5 cluster nodes (one at a time) without success.
g
for some reason the ingress rule is missing in the support bundle
creating that rule should get the UI to work