IFS-Remote Upgrade Process¶

Prerequisites¶

• Download IFS-Remote Infrastructure artifacts from a “IFS Support as of Middle Tier version“ or later, described in the Supported Platforms documentation for Middle-Tier server.

  1. Download ifs-remote-x.y.z.zip of the desired IFS Cloud version by clicking the “Remote Bootstrap Zip” button in the LE portal.
  2. Download ifs-remote-bin-x.y.z.zip of the desired IFS Cloud version by clicking the “Remote Bootstrap Binaries Zip” button in the LE portal.

• Prepare Middle-Tier server

  • Deploy a New Ubuntu Server 22.04 LTS with latest Security Patches from IT replacing the existing Middle-Tier Server VM Install Middle Tier Server - Technical Documentation For IFS Cloud.

    or;

  • Upgrade the Existing Ubuntu Server 20.04 LTS Middle-Tier Server VM to Ubuntu Server 22.04 LTS with latest Security Patches as mentioned in Ubuntu release upgrade documentation.

Steps to Upgrade IFS-Remote¶

1. Upgrade IFS-Remote infrastructure:

   1. Create a new folder.

   2. Copy the downloaded ifs-remote-x.y.z.zip from into the new folder.

   3. Copy the downloaded ifs-remote-bin-x.y.z.zip into the new folder.

   4. Unblock the ifs-remote-x.y.z.zip and ifs-remote-bin-x.y.z.zip.

   5. Extract both zip files into the current directory.

   6. You would find the new ifsroot folder.

   7. Copy ifsroot/config/main_config.json.template file into ifsroot/config/main_config.json.

   8. The next step is to update the ifsroot/config/main_config.json file with environment specific values, reviewing the old ifsroot/config/main_config.json. Refer the Main Configuration Parameters File.

   New Configuration Parameters (available from version 3.0.15): - Ifs.IngressController: Specifies which ingress controller to use ("Nginx" or "Traefik"). Defaults to "Nginx" for backward compatibility with existing installations. - Ifs.IngressPort: Configures the HTTPS port for the ingress controller. Defaults to 443. Useful when deploying Traefik with unprivileged ports (e.g., 8443). - Ifs.AllowPrivilegedPorts: Controls whether the ingress controller can bind to privileged ports (< 1024). Defaults to true. Set to false when using unprivileged ports; requires external load balancer for port mapping.

   Backward Compatibility Note: Existing installations will continue using Nginx ingress controller with port 443 unless these parameters are explicitly modified. The default values ensure no changes are required for existing deployments.

   1. The kubernetes cluster has to be recreated by running the scripts described in quick installation or custom installation guide.
      NOTE: When PrivilegedLinuxUser is false, a privileged administrator must unlock the artifacts on each node before step 9, and lock them again afterwards. See Updating Artifacts with PrivilegedLinuxUser=false

2. Install IFS Cloud. Refer to the documentation here.

3. Install Monitoring. Refer to the documentation here.