ON THIS PAGE
Migration from a Single-Master Setup to a Multi-Master Setup
Paragon Insights does not support an upgrade from a single-master setup to a multi-master setup. With Paragon Insights Release 4.0.0, you can only migrate from a single-master setup to a multi-master setup.
These topics provide information on migration.
Before You Begin
For production deployments, it is recommended that you have dedicated master nodes for the Kubernetes control plane.
All prerequisites (node-related) provided in the Paragon Insights Installation Requirements topic are met.
Steps for Migration
Follow these steps to migrate from a single-master setup to a multi-master setup
Multi-NIC
Paragon Insights Release 4.0.0 supports multi-NIC (network interface card).
In a scenario where telemetry information of devices that you
are monitoring is generated from one network, and you access the web
UI from another network, Paragon Insights allows you to enter multiple
virtual IP addresses when you run the healthbot setup
. This
ensures segregation of traffic between the networks.
For this feature to work, you will need multiple virtual IP addresses for every
subnet. Virtual IP addresses for these subnets can be provided when you run healthbot
setup
.
For example, when you run healthbot setup
, you are prompted to enter a virtual IP address. In this case, you must enter
more than one virtual IP address. After you run healthbot start
, all services will be available on all virtual IP addresses.