This message was deleted.
# harvester
a
This message was deleted.
g
which rc did you use?
b
rc3. However, I stopped trying and went to 1.2.1 and all is well
👍 1
g
i will check if anyone else has seen the error in rc3, i have been using rc3 a lot and never ran into this error
did you use install mode?
or just normal create/join?
b
no worries. It’s totally not a priority for me. Normal create
g
thanks
b
The biggest priority I have is one of latter questions regarding a hook to trigger a call to an API if a node goes offline and a new one picks up the VIP. If you have any insight there, I’d apprecaite it, otherwise no worries!
g
the vip should failover to another node
b
yes, but I need the new node to make an API call out to the internet when this happens
g
first time this has been asked and I am not sure
b
as the VIP stuff happens with gratuitous arping. I need to do an additional step
ok, thanks
g
may be an alertmanager rule if there is a way to identify where ip is attached
b
basically if there is some sort of event that triggers when one of the slave nodes assumes master, it can make the API call. I can attempt to write what is needed, I just need to have more insight into how it all works
g
is it possible to create an issue on github as well
makes it easy to track and identify if others have similar requirement too
b
will do tomorrow. Thanks!
👍 1
today is the new tomorrow
g
thanks