Upgrade considerations for Component Pack 8 CR3
The upgrade path described in Steps to install or upgrade to Component Pack 8 CR3 is based on a given set of components, versions, and goals. Consider the following information when deciding how best to upgrade based on your deployment and needs.
Side-by-side vs. in-place
You can upgrade to HCL Connections 8.0 CR3 by doing either a side-by-side or an in-place upgrade. The approach described in Steps to install or upgrade to Component Pack 8 CR3 focuses on upgrading Connections 7 to 8 on the same set of machines. This involves an in-place upgrade of an existing Kubernetes environment by touching file shares, and Helm release and charts.
If your upgrade strategy requires a side-by-side migration on a mirrored set of both WebSphere and Kubernetes machines, you can still use the installation document. The difference between the two approaches is the transfer of data from source to destination system.
For a side-by-side migration, these would be the steps:
- Set up a mirrored WebSphere system with the same version as the source system
- Migrate or switch file shares and databases
- Migrate Connections or Docs configuration between the two systems
- In-place upgrade of the mirrored WebSphere Application Server (set) by touching the database, WebSphere, HTTP Server components, and Connections
- Set up a mirrored Kubernetes system with the same version as the source system
- Migrate or switch file shares (PVs) between the two systems
- In-place upgrade of the mirrored Kubernetes environment by touching file shares, and Helm release and charts
For more information, see Upgrade considerations for side-by-side migration of data.
To deploy Component Pack, we use the Harbor container registry. Modify the reference according to your environment. When provisioning Component Pack 8 CR3, you can empty your local Docker repository or manually delete the Connections 7 parts before starting the upgrade to version 8 CR3.
Switch container runtime
Ensure containerd is up and running on Kubernetes master and worker nodes. Follow the steps in migrating from Docker to containerd.
Watch out for the --network-plugin flag. You will need to remove it from /var/lib/kubelet/kubeadm-flags.env, otherwise kublet won't start after upgrading to v1.24. For details, view the GitHub issue.
Note: Since we switched the container runtime from Docker to containerd, there is a possibility that all pods will show status as 'ImagePullBackOff'.
If your Component Pack services run on an unsupported Kubernetes version, upgrade to a supported version before moving to Connections 8.0 CR3. Refer to HCL Connections 8.0 CR3 System Requirements.
During the installation scenario, we will upgrade our Kubernetes stack to the newest Connections Component Pack release. This will impact the cpmaster.example.com machine, which runs the containerized modules.
Connections 8.0 CR3 defines OpenSearch 1.3.0 as the default backend for Orient Me, search and Metrics – this is what we'll deploy and configure in our installation scenario. Previous Connections releases used an older Elasticsearch 7 version, which is no longer needed.
Note: In case you already have Metrics deployed and its data collected, and you do not want to start Metrics from scratch, you will have to migrate these data into the new release. Steps to install or upgrade to Component Pack 8 CR3 covers both scenarios.
Parent topic: Installation and upgrade