Upgrade from 2.X to 3.X
If you are on a 2.X release of HealthBot and want to move to 3.1.0 release with a multi-node (Kubernetes) installation, you must do a fresh installation. To migrate your data from HealthBot Release 2.X (docker-compose) to 3.1.0 (Kubernetes) follow the procedure here: Migration from HealthBot Release 2.X to 3.X. This issue does not apply if upgrading from release 3.0.0/3.0.1 to release 3.1.0
User Credentials from 2.X
Any user credentials present prior to upgrade from 2.X must be recreated after upgrade from release 2.X to release 3.2.0. This issue does not apply if upgrading from release 3.X to release 3.2.0
The RBAC feature is limited to providing either read-only or read-write access to all pages for any user except the hbadmin user. Fine grained access to pages or features is not controlled in this release.
Retaining Graph and Timeline View Data
In some cases, Graph and timeline view data is not retained during an upgrade or migration from release 2.X to 3.X. To deal with this issue, click Deploy in the left-nav before performing an upgrade. This issue does not apply when upgrading from release 3.0.0/3.0.1 to release 3.2.0
No documentation support is provided for the HealthBot CLI. Contact a Juniper Networks representative for support.