Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Upgrading Paragon Insights Release 3.X with Kubernetes-based Installation to Release 4.X

Note:

You can upgrade only Paragon Insights (formerly HealthBot) Release 3.X with Kubernetes-based installation to Release 4.X. You cannot upgrade a Docker Compose-based installation to Release 4.X.

If your are currently using Paragon Insights with Docker Compose-based installation, then you must perform a fresh installation of Release 4.X. To perform a fresh installation of Paragon Insights or to upgrade Paragon Insights 4.X to a later release, see Using the Interactive Installers to Install or Upgrade to Paragon Insights Release 4.X or Using the Silent Installer topics.

To upgrade from Paragon Insights Release 3.x with Kubernetes-based installation to Paragon Insights Release 4.x:

  1. Take a backup of the keycloak-hb.json file. To take a backup:
    1. Identify the keycloak pod in the namespace.
    2. Connect to the keycloak pod.
    3. Run the following command to generate the backup file:
    4. Terminate the process using ctrl-c after you receive the following message:
    5. Disconnect from the keycloak pod and copy the file from the Keycloak pod to your local system.
  2. Follow the instructions mentioned in Using the Interactive Installers to Install or Upgrade to Paragon Insights Release 4.X to upgrade to Paragon Insights Release 4.X.
    Note:

    When you run the sudo healthbot setup command, you need not enter the installation configuration as the installer already has the required information.
  3. Log in to the GUI.

    The default password for the admin user is Admin123! and the admin user must reset the password on first login. The default password for users other than the admin user is Change123!.

  4. If you are the admin user, you can import the user configuration to Paragon Insights Release 4.X using the following command:

You are now upgraded to Paragon Insights Release 4.X and you have migrated the data.

The following are the changes after you upgrade and migrate your data to Paragon Insights Release 4.X:

  • The existing users of Paragon Insights Release 3.X.X are added to the IAM server. However, the existing user’s credentials are not migrated.

  • The existing user roles of Paragon Insights Release 3.X.X are not migrated. The existing user is mapped to default roles that are available in Paragon Insights Release 4.X.

  • The existing user groups of Paragon Insights Release 3.X.X are not migrated. The existing user groups are associated with a default role, that is, the hbadmin user group will be migrated with the default role of sp-admin and any other groups will be migrated with role of sp-operator. After the upgrade is complete, the administrator can manually reconfigure the group permission.

Note:

If you are using LDAP (Lightweight Directory Access), users and user groups are not added to the LDAP server.