Upgrading Component Pack 6.5 to 6.5 CR1

Upgrade the HCL Connections™ Component Pack 6.5 to the latest version, 6.5 CR1.

Before you begin

Upgrading bootstrap

In Component Pack 6.5 CR1, you must regenerate the certificates for Elasticsearch. Since bootstrap is already deployed, you must first purge the previous bootstrap helm release and then install the bootstrap again by running the following commands.

  • Find the helm values of bootstrap that are set on the current installation:
    helm get values bootstrap
    Note: Remember to record the values returned.
  • Purge the previous bootstrap:
    helm delete bootstrap --purge
  • Install bootstrap again by following the steps in Bootstrapping the Kubernetes cluster.

Purging the bootstrap will not remove any secrets or certificates if it has detected that there is a service using them. In case of emergency, you can force the bootstrap to regenerate secrets and certificates by using the helm value env.force_regenerate=true when installing bootstrap.

Upgrading connections-env

To upgrade connections-env, run the following command:

helm upgrade connections-env extractedFolder/microservices_connections/hybridcloud/helmbuilds/connections-env-0.1.40-20200320-143558.tgz \
--set <args_from_initial_install>

where <args_from_initial_install> is the same helm values that are set on the current installation. If you do not specify these values, the helm upgrade will reset values to their default. You can determine the values used during the initial install by running helm get values connections-env.

Installing/upgrading cnx-ingress

This helm chart is new from the 6.0.0.7 release and thus should not be deployed with 6.0.0.6. cnx-ingress is required for Orient Me, Customizer, and Sanity. If upgrading from 6.0.0.6, follow the installation instructions in this topic Installing Ingress Controller.

If upgrading from 6.0.0.7 onwards, run the following command:
helm upgrade cnx-ingress extractedFolder/microservices_connections/hybridcloud/helmbuilds/cnx-ingress-0.1.0-20200320-150203.tgz \
--set <args_from_initial_install>
where <args_from_initial_install> is the same helm values that are set on the current installation. If you do not specify these values, the helm upgrade will reset values to their default. You can determine the values used during the initial install by running helm get values cnx-ingress.

Upgrading infrastructure

To upgrade the infrastructure, run the following command:

helm upgrade infrastructure extractedFolder/microservices_connections/hybridcloud/helmbuilds/infrastructure-0.1.0-20200321-173948.tgz \
--set <args_from_initial_install>

where <args_from_initial_install> is the same helm values that are set on the current installation. If you do not specify these values, the helm upgrade will reset values to their default. You can determine the values used during the initial install by running helm get values infrastructure.

Upgrading orientme

To upgrade orientme, run the following command:

helm upgrade orientme extractedFolder/microservices_connections/hybridcloud/helmbuilds/orientme-0.1.0-20200321-174037.tgz \
--force --set <args_from_initial_install>

where <args_from_initial_install> is the same helm values that are set on the current installation. If you do not specify these values, the helm upgrade will reset values to their default. You can determine the values used during the initial install by running helm get values infrastructure helm get values orientme.

Upgrading elasticsearch

To upgrade elasticsearch, run the following command:

helm upgrade elasticsearch extractedFolder/microservices_connections/hybridcloud/helmbuilds/elasticsearch-0.1.0-20200319-223218.tgz \
--force --set <args_from_initial_install>

where <args_from_initial_install> is the same helm values that are set on the current installation. If you do not specify these values, the helm upgrade will reset values to their default. You can determine the values used during the initial install by running helm get values elasticsearch.

Upgrading mw-proxy (Customizer)

To upgrade mw-proxy, run the following command:

helm upgrade mw-proxy extractedFolder/microservices_connections/hybridcloud/helmbuilds/mw-proxy-0.1.0-20200321-114108.tgz \
--force --set <args_from_initial_install>

where <args_from_initial_install> is the same helm values that are set on the current installation. If you do not specify these values, the helm upgrade will reset values to their default. You can determine the values used during the initial install by running helm get values mw-proxy.

Upgrading sanity

To upgrade sanity, run the following command:

helm upgrade sanity extractedFolder/microservices_connections/hybridcloud/helmbuilds/sanity-0.1.8-20200321-160144.tgz \
--force --set logLevel=info,\
<args_from_initial_install>

where <args_from_initial_install> is the same helm values that are set on the current installation. If you do not specify these values, the helm upgrade will reset values to their default. You can determine the values used during the initial install by running helm get values sanity.

Upgrading sanity-watcher

To upgrade sanity-watcher, run the following command:

helm upgrade sanity-watcher extractedFolder/microservices_connections/hybridcloud/helmbuilds/sanity-watcher-0.1.0-20200218-182137.tgz \
--force --set <args_from_initial_install>

where <args_from_initial_install> is the same helm values that are set on the current installation. If you do not specify these values, the helm upgrade will reset values to their default. You can determine the values used during the initial install by running helm get values sanity-watcher.

Upgrading elasticstack

To upgrade elasticstack, run the following command:

helm upgrade elasticstack extractedFolder/microservices_connections/hybridcloud/helmbuilds/elasticstack-0.1.0-20191122-115449.tgz \
--force --set <args_from_initial_install>

where <args_from_initial_install> is the same helm values that are set on the current installation. If you do not specify these values, the helm upgrade will reset values to their default. You can determine the values used during the initial install by running helm get values elasticstack.

Hardening Persistent Volume Permissions

As part of previous release PV set up, it was required to set the/pv-connections directory up with world read/writable permissions. In the 6.0.0.7 release and onwards, you now only need to set permissions so that owner can read, write and execute. For the customizer PV, you need to set permissions so that others can read and execute. Run the following commands on your storage server to make the change:
sudo chmod -R 700 /pv-connections
sudo chmod -R 005 /pv-connections/customizations
Note: As services run, the directory and file permissions will be changed by the container users.

What to do next

Upgrade the Kubernetes cluster to v1.17.2. For information on a validated setup, see Kubernetes reference implementation.