https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
p
We need to change the static IP down due to an oversight in our IP convention
@witty-jelly-95845 Any suggestions?
w
Do you have one node or multiple ?
p
Currently we have 2 nodes
w
According to https://github.com/harvester/harvester/issues/2063#issuecomment-1094281911 theoretically VIP could be changed but ...
p
Welp time to rebuild for the second time
I scaled down to a single harvester instance
Our node IP is fine
w
I've found VIP using kubectl 
kubectl get service -n kube-system ingress-expose
but I'm not about to try changing that without more digging (it must be configured somewhere so nodes know what to talk to) plus I need my cluster working right now!
p
That worked
I found all references to the old ip and changed it
w
Well I suppose if you're going to reinstall anyway 🤓
p
We just need to reinstall our other nodes
kubectl get all -o yaml --all-namespaces | grep "old_ip"
though I hear 
kubectl get all
is deprecated
kubectl edit configmaps -n harvester-system vip
You also have to delete 
serving-cert
and restart internal rancher
w
Re 
kubectl get all
being deprecated, https://github.com/kubernetes/kubectl/issues/151 was an interesting read!
100 Views
Open in Slack
PreviousNext
Powered by