Upgrading Local Edition Cluster from 5.4.1 to 5.5.0 for Kubernetes in Tethered Mode

The following section provides information on upgrading Local Edition cluster from version 5.4.1 to 5.5. for Kubernetes in Tethered mode.

Prerequisites

  • Local Edition 5.5.0 images must be built and pushed to the desired registry for deployment.
  • The volumes for tml-nosql, tml-logtml-cache are reused, so while doing upgrade the number of these pods must be consistent with the earlier version.
  • The customization done to the JSON properties files in earlier version must be ported to 5.5.0.
  • Admin must generate the manifest deployment folder, namely the manifest-single-zone, as per the deployment topology for version 5.4.1 by running the compose command.
Note:
  • The following procedure is applicable for single and multi zone clusters.
  • Some traffic disruptions are expected during upgrade. To minimize disruptions, upgrade theLocal Edition components sequentially, explained as follows.

Procedure

  1. Undeploy and redeploy NoSQL components.
    1. Remove running Local Edition 5.4.1 NoSQL container. Run the following command.
      • For single-zone deployment: 
        ./undeploy-nosql-pod.sh
    2. Deploy Local Edition 5.5.0 NoSQL containers. Run the following command.
      • For single-zone deployment: 
        ./deploy-nosql-pod.sh
  2. Undeploy and redeploy Log components.
    1. Remove running Local Edition 5.4.1 Log container. Run the following command.
      • For single-zone deployment: 
        ./undeploy-log-pod.sh
    2. Deploy Local Edition 5.5.0 Log containers. Run the following command.
      • For single-zone deployment: 
        ./deploy-log-pod.sh
  3. Undeploy and redeploy CM components.
    1. Remove running Local Edition 5.4.1 CM container. Run the following command. 
      • ./undeploy-cm-pod.sh
    2. Deploy Local Edition 5.5.0 CM containers. Run the following command. 
      • ./deploy-cm-pod.sh
  4. Undeploy and redeploy SQL components.

    The MySQL Certificate/Identity data migration for tethered mode works for the following migration cases:

    • 5.3.1 to 5.4.1
    • 5.3.1 to 5.5.0
    • 5.4.1 to 5.5.0

    Please complete the Certificate/Identity data migration as soon as the new cluster is deployed, otherwise new certificates/identities created in the new6 /blop cluster will be overwritten by data migration.

    1. Dump MySQL Data from the cluster created in the earlier version. Login to any tml-sql pod running in the earlier cluster. 
      kubectl exec mysql-set-0-0 -- mysqldump --no-create-info --complete-insert --single-transaction -u root -p'changeme' masherysolar trust_store identity_store > mash_data.sql
    2. Remove the SQL container from the 5.4.1 cluster.
      For single zone deployment, 
      ./undeploy-sql-pod.sh
      Note: Delete SQL pvc after undeploying the SQL pod, 
      kubectl delete pvc $(kubectl get pvc -o=jsonpath='{.items[?(@.metadata.labels.app=="mysql-svc")].metadata.name}')
    3. Deploy Mashery Local 5.5.0 SQL containers. Run the following command.
      For single zone deployment, 
      ./deploy-sql-pod.sh
  5. Copy the MySQL data from 5.4.0 cluster in the 5.5.0 cluster.
    Run the following command to copy MySQL data file to any tml-sql pod in TML 5.5.0 cluster 
    kubectl cp mash_data.sql mysql-set-0-0:/tmp
    Note: The mysql-set-0-0 is thetml-sql pod in the new cluster.
  6. Import MySQL data dumped from the 5.4.1 cluster to the 5.5.0 cluster.

    Run the following command in each tml-sql pod in the new cluster. 

    mysql -u root -p'changeme' -e "truncate table masherysolar.trust_store"
mysql -u root -p'changeme' -e "truncate table masherysolar.identity_store"
mysql -u root -p'changeme' masherysolar < /tmp/mash531_data.sql
  7. Run the SQL loader in sql pods in the new TML Cluster.

    Run the following command in eachtml-sql to run the sql loader. 

    /opt/sqlloader/onpremloader --service --mapi --devclass --packager --httpsclientsecurity --env production --verbose
  8. Undeploy and redeploy Cache components.
    Remove running Local Edition 5.4.1 Cache container.
    1. For single zone undeployment: 
      • ./undeploy-cache-pod.sh
    2. To redeploy the container, run the following command. 
      ./deploy-cache-pod.sh
  9. Undeploy and redeploy TM components.
    Remove running Local Edition 5.4.0 TM container.
    1. For single zone undeployment: 
      • ./undeploy-tm-pod.sh
    2. Deploy TM container, run the following command. 
      ./deploy-tm-pod.sh
  10. Note: This is applicable if reporting pod is deployed.
    Undeploy and redeploy Reporting components.
    Remove running Local Edition 5.4.1 TM container.
    1. For single zone undeployment: 
      • ./undeploy-reporting-pod.sh
    2. Deploy 5.5.0 TM container, run the following command. 
      ./deploy-reporting-pod.sh