The following is a list of known issues in HealthBot Release 3.0.1:
If you want to do a multi-node installation of HealthBot Release 3.0.1 (Kubernetes) you must do a fresh installation. To migrate your data from HealthBot Release 2.X (docker-compose) to 3.0.1 (Kubernetes) follow the procedure here: Migration from HealthBot Release 2.X to 3.X.
A multi-node installation of HealthBot Release 3.0.1 cannot be performed on an existing Kubernetes cluster. You must allow the installer to create a new Kubernetes cluster. Support for installation on exiting Kubernetes clusters is planned for a future release.
The addition of RBAC features requires that any user credentials present prior to upgrade must be recreated after upgrade from release 2.X to release 3.0.X. This issue does not apply if upgrading from release 3.0.0 to 3.0.1.
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.
In some cases, Graph and timeline view data is not retained during an upgrade or migration from release 2.X to 3.0.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 to release 3.0.1.
During HealthBot remove or install operations on RPM-based (CentOS or RedHat) servers, a lot of warnings are shown on the terminal regarding inability to remove files because they are not found. These warnings can be ignored.
No documentation support is provided for the HealthBot CLI. Contact a Juniper Networks representative for support.