Points to Remember

  • Do not use the appviewx_kubernetes installer if it was previously used during the upgrade process. During the upgrade, the initial seed dump file is replaced with the user-provided backup file, which could lead to issues if the same installer is reused for a fresh installation. To ensure a smooth process, always use a new appviewx_kubernetes installer for fresh installations.
  • The file <installer path>/interactive-iu/resources/requirements.txt located inside the interactive-iu folder is just a reference for prerequisites validation during the upgrade. Do not use it for package installation.
  • If auto-enrolment plugins are selected during the installation phase, the external gateway must be installed manually.
  • Navigating back to previous questions after reaching the additional questions requires exiting and restarting the process.
  • Latency warnings during prerequisite checks can be ignored. However, it is recommended to manually verify latency using the ping command for confirmation.
  • For a patch rollback, update the addons_backup_path and plugins_backup_path in the application_upgrade.json file located in the <appviewx_installer>/scripts folder if multiple backups are present. Backup paths can be found in the <appviewx_installer>/backups directory.
  • Additional questions have been introduced during the production cut-over; however, they are consistently restricted to "No," ensuring they do not impact the cut-over process.