This message originated from Cribl Community Slack.
Click here to view the original link.
Hi everybody, I'm migrating my clients infra to a new datacenter (leader node + central worker group and multiple worker nodes).
What is in your opinion the best way, to migrate the LN?
It will be a new VM with new ip/dns
Solved
Migration Strategy Needed For Leader Node To New VM With New IP/DNS
Best answer by Jon Rust
Leader:
- update the existing leader to latest
- install a fresh leader package and set-up the boot start config
- archive/restore the previous install on top of this new install
- validate new leader is running and no firewalls, proxies, etc are in the way
- There is no benefit to moving installs from old workers -- start fresh
- Follow normal install procedure for workers
- Ensure your load balancers, firewalls, etc are pointing to the new worker nodes
Leader:
- update the existing leader to latest
- install a fresh leader package and set-up the boot start config
- archive/restore the previous install on top of this new install
- validate new leader is running and no firewalls, proxies, etc are in the way
- There is no benefit to moving installs from old workers -- start fresh
- Follow normal install procedure for workers
- Ensure your load balancers, firewalls, etc are pointing to the new worker nodes
Thanks Jon. The current leader node uses gitops. Is it possible to connect the new leader and restore from the repo?
i believe yes. Not sure of the specifics tho
Sign up
Already have an account? Login
Login to the community
No account yet? Create an account
Using your Cribl Curious or University Account
User Login Employee loginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.