Console Migration

We recommend that you complete Kato and cluster deployment through Quick Deployment, and after you have basically experienced Kato, migrate the console of stand-alone deployment to Kato for management.

Deploy the Console to Kato

Before starting deployment, make sure that the remaining memory resources of the cluster are greater than 2GB.

First, still visit the Kato console and create a system service team to deploy system applications. Enter the team space and choose to add, create components based on the application market. Search for kato in the open source app store to find the Kato-open source application.

Please note that if you have not completed the application store binding, please register and log in to the cloud application store in the enterprise view application store management.

Click Install, select the latest version (5.3.0 is the latest version that supports this deployment mode) to complete the deployment of the Kato console. After the console is successfully started, you can access the new console through the default domain name. Complete the registration of the administrator account in the new console to enter the data recovery page.

Please note that if you need to use a cloud database or a self-built highly available database, you can replace the Mysql database component in the installed application after adding an external database through a third-party component. The connection variable information in the third-party component needs to be consistent with the Mysql component.

Kato-UI and Kato-Console can be horizontally extended and retracted.

Back up the data of the old console

Go back to the enterprise view of the old console-“Settings page, switch to the data backup page. As shown below:

Click Add Backup to back up the latest data of the old console.

After the backup is successful, a backup record will appear as shown in the figure above. Click Download to download the backup data to the local for backup.

If you click to download and there is no response, it may be that your browser (such as Google) has rejected the download action. Please change your browser and try again.

Import data to the new console

Visit the new console deployed in Kato, also enter the data backup page, click Import Backup, and upload the backup data downloaded in the previous step.

Please note that you must ensure that the source console version of the backup data is consistent with the new console version.

After the upload is successful, click Restore to import the data into the new console. After successful recovery, you need to log out and log in with the account information of the old console. You will find that the data has been migrated successfully.

Please note that if the platform automatically logs out after recovery, please re-visit the domain name of the new console, do not carry the path path, and log in with the account of the old console. Because the historical data has become invalid.

At this point, the console migration has been completed. You can use the platform gateway policy management to bind your own domain name or TCP policy to the console. Reference Document

  • Please pay attention to regularly back up the platform data to facilitate the recovery of console services in an emergency.

  • Please remember the grctl service get query command in the scaling management page for all components of the console, which helps to operate the component on the cluster side in an emergency.