Upgrade SMM - GitOps - single cluster

This document describes how to upgrade SMM and a business application.

Prerequisites

To complete this procedure, you need:

• A free registration for the Service Mesh Manager download page
• A Kubernetes cluster running Argo CD (called management-cluster in the examples).
• A Kubernetes cluster running the previous version of Service Mesh Manager (called workload-cluster-1 in the examples). It is assumed that Service Mesh Manager has been installed on this cluster as described in the Service Mesh Manager 1.10.0 documentation, and that the cluster meets the resource requirements of Service Mesh Manager version 1.11.0.

This document describes how to upgrade Service Mesh Manager version 1.10.0 to Service Mesh Manager version 1.11.0.

Set up the environment

1. Set the KUBECONFIG location and context name for the management-cluster cluster.

   MANAGEMENT_CLUSTER_KUBECONFIG=management_cluster_kubeconfig.yaml
   MANAGEMENT_CLUSTER_CONTEXT=management-cluster
   kubectl config --kubeconfig "${MANAGEMENT_CLUSTER_KUBECONFIG}" get-contexts "${MANAGEMENT_CLUSTER_CONTEXT}"
   

   Expected output:

   CURRENT   NAME                 CLUSTER              AUTHINFO   NAMESPACE
   *         management-cluster   management-cluster
   

2. Set the KUBECONFIG location and context name for the workload-cluster-1 cluster.

   WORKLOAD_CLUSTER_1_KUBECONFIG=workload_cluster_1_kubeconfig.yaml
   WORKLOAD_CLUSTER_1_CONTEXT=workload-cluster-1
   kubectl config --kubeconfig "${WORKLOAD_CLUSTER_1_KUBECONFIG}" get-contexts "${WORKLOAD_CLUSTER_1_CONTEXT}"
   

   Expected output:

   CURRENT   NAME                 CLUSTER              AUTHINFO                                          NAMESPACE
   *         workload-cluster-1   workload-cluster-1
   

   Repeat this step for any additional workload clusters you want to use.

3. Make sure the management-cluster Kubernetes context is the current context.

   kubectl config --kubeconfig "${MANAGEMENT_CLUSTER_KUBECONFIG}" use-context "${MANAGEMENT_CLUSTER_CONTEXT}"
   

   Expected output:

   Switched to context "management-cluster".
   

Upgrade Service Mesh Manager

The high-level steps of the upgrade process are:

• Install the new IstioControlPlane istio-cp-v115x on the workload cluster.
• Upgrade the smm-operator and the smm-controlplane. The smm-controlplane will use the new istio-cp-v115x IstioControlPlane, but the business applications (for example, demo-app) will still use the old istio-cp-v113x control plane.
• Upgrade the business applications (demo-app) to use the new control plane.

1. Remove the old version (1.10.0) of the smm-operator Helm chart.

   rm -rf charts/smm-operator
   

2. Pull the new version (1.11.0) of the smm-operator Helm chart and extract it into the charts folder.

   helm pull oci://registry.eticloud.io/smm-charts/smm-operator --destination ./charts/ --untar --version 1.11.0
   

3. Create the istio-cp-v115x.yaml file.

   cat > manifests/istio-cp-v115x.yaml << EOF
   apiVersion: servicemesh.cisco.com/v1alpha1
   kind: IstioControlPlane
   metadata:
     annotations:
       argocd.argoproj.io/sync-wave: "5"
     name: cp-v115x
     namespace: istio-system
   spec:
     containerImageConfiguration:
       imagePullPolicy: Always
       imagePullSecrets:
       - name: smm-pull-secret
     distribution: cisco
     istiod:
       deployment:
         env:
         - name: ISTIO_MULTIROOT_MESH
           value: "true"
         image: registry.eticloud.io/smm/istio-pilot:v1.15.3-bzc.0
     k8sResourceOverlays:
     - groupVersionKind:
         group: apps
         kind: Deployment
         version: v1
       objectKey:
         name: istiod-cp-v115x
         namespace: istio-system
       patches:
       - path: /spec/template/spec/containers/0/args/-
         type: replace
         value: --tls-cipher-suites=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256
     meshConfig:
       defaultConfig:
         envoyAccessLogService:
           address: smm-als.smm-system.svc.cluster.local:50600
           tcpKeepalive:
             interval: 10s
             probes: 3
             time: 10s
           tlsSettings:
             mode: ISTIO_MUTUAL
         holdApplicationUntilProxyStarts: true
         proxyMetadata:
           ISTIO_META_ALS_ENABLED: "true"
           PROXY_CONFIG_XDS_AGENT: "true"
         tracing:
           tlsSettings:
             mode: ISTIO_MUTUAL
           zipkin:
             address: smm-zipkin.smm-system.svc.cluster.local:59411
       enableEnvoyAccessLogService: true
       enableTracing: true
     meshExpansion:
       enabled: true
       gateway:
         deployment:
           podMetadata:
             labels:
               app: istio-meshexpansion-gateway
               istio: meshexpansiongateway
         service:
           ports:
           - name: tcp-smm-als-tls
             port: 50600
             protocol: TCP
             targetPort: 50600
           - name: tcp-smm-zipkin-tls
             port: 59411
             protocol: TCP
             targetPort: 59411
     meshID: mesh1
     mode: ACTIVE
     networkName: network1
     proxy:
       image: registry.eticloud.io/smm/istio-proxyv2:v1.15.3-bzc.0
     proxyInit:
       cni:
         daemonset:
           image: registry.eticloud.io/smm/istio-install-cni:v1.15.3-bzc.0
       image: registry.eticloud.io/smm/istio-proxyv2:v1.15.3-bzc.0
     sidecarInjector:
       deployment:
         image: registry.eticloud.io/smm/istio-sidecar-injector:v1.15.3-bzc.0
     version: 1.15.3
   EOF
   

4. Update the smm-controlplane.yaml file to use the istio-cp-v115x IstioControlPlane.

   cat > manifests/smm-controlplane.yaml << EOF
   apiVersion: smm.cisco.com/v1alpha1
   kind: ControlPlane
   metadata:
     annotations:
       argocd.argoproj.io/sync-wave: "10"
     name: smm
   spec:
     certManager:
       enabled: true
       namespace: cert-manager
     clusterName: workload-cluster-1
     clusterRegistry:
       enabled: true
       namespace: cluster-registry
     log: {}
     meshManager:
       enabled: true
       istio:
         enabled: true
         istioCRRef:
           name: cp-v115x
           namespace: istio-system
         operators:
           namespace: smm-system
       namespace: smm-system
     nodeExporter:
       enabled: true
       namespace: smm-system
       psp:
         enabled: false
       rbac:
         enabled: true
     oneEye: {}
     registryAccess:
       enabled: true
       imagePullSecretsController: {}
       namespace: smm-registry-access
       pullSecrets:
       - name: smm-registry.eticloud.io-pull-secret
         namespace: smm-registry-access
     repositoryOverride:
       host: registry.eticloud.io
       prefix: smm
     role: active
     smm:
       exposeDashboard:
         meshGateway:
           enabled: true
       als:
         enabled: true
         log: {}
       application:
         enabled: true
         log: {}
       auth:
         forceUnsecureCookies: true
         mode: anonymous
       certManager:
         enabled: true
       enabled: true
       federationGateway:
         enabled: true
         name: smm
         service:
           enabled: true
           name: smm-federation-gateway
           port: 80
       federationGatewayOperator:
         enabled: true
       impersonation:
         enabled: true
       istio:
         revision: cp-v115x.istio-system
       leo:
         enabled: true
         log: {}
       log: {}
       namespace: smm-system
       prometheus:
         enabled: true
         replicas: 1
       prometheusOperator: {}
       releaseName: smm
       role: active
       sre:
         enabled: true
       useIstioResources: true
   EOF
   

5. If you are upgrading Service Mesh Manager 1.10.0 to 1.11.0: complete this step, otherwise skip to the next step.

   Apply the following patch to your Service Mesh Manager v1.10.0 cluster to modify the spec field of a job that cleans up the cert-manager-startupapicheck job after 100 seconds when completed. If you skip this step, you might see a cert-manager-startupapicheck related error during the upgrade.

   kubectl patch jobs.batch -n cert-manager cert-manager-startupapicheck -p '{"spec":{"ttlSecondsAfterFinished":100}}' --type=merge --kubeconfig "${WORKLOAD_CLUSTER_1_KUBECONFIG}" --context "${WORKLOAD_CLUSTER_1_CONTEXT}"
   

6. Commit and push the changes to the Git repository.

   git add .
   
   git commit -m "upgrade smm to 1.11.0"
   
   git push
   

7. Wait a few minutes, then check the new IstioControlPlane.

   kubectl -n istio-system get istiocontrolplanes.servicemesh.cisco.com --kubeconfig "${WORKLOAD_CLUSTER_1_KUBECONFIG}" --context "${WORKLOAD_CLUSTER_1_CONTEXT}" 
   

   Expected output:

   NAME       MODE     NETWORK    STATUS      MESH EXPANSION   EXPANSION GW IPS                    ERROR   AGE
   cp-v113x   ACTIVE   network1   Available   true             ["52.208.63.154","54.155.81.181"]           61m
   cp-v115x   ACTIVE   network1   Available   true             ["52.211.44.215","63.32.253.55"]            11m
   

8. Open the Service Mesh Manager dashboard.

   On the MENU > OVERVIEW page everything should be fine, except for some validation issues. The validation issues show that the business application (demo-app) is behind the smm-control-plane and the business application should be updated to use the latest IstioControlPlane.

   

   

   You can see the two IstioControlPlanes on the MENU > MESH page. The smm-control-plane is using the cp-v115x.istio-system IstioControlPlane and the demo-app is using the cp-v113x.istio-system IstioControlPlane.

   

Upgrade Demo application

The demo-app application is just for demonstration purposes, but it represents your business applications. To upgrade a business application, set the istio.io/rev label of the business application’s namespace to the target IstioControlPlane. Complete the following steps to update the demo-app to use the cp-v115x.istio-system IstioControlPlane and set the istio.io/rev label accordingly.

1. Update the label on you application namespace (for the demo application, that’s the demo-app-ns.yaml file).

   cat > demo-app/demo-app-ns.yaml << EOF
   apiVersion: v1
   kind: Namespace
   metadata:
     labels:
       app.kubernetes.io/instance: smm-demo
       app.kubernetes.io/name: smm-demo
       app.kubernetes.io/part-of: smm-demo
       app.kubernetes.io/version: 0.1.4
       istio.io/rev: cp-v115x.istio-system
     name: smm-demo
   EOF
   

2. Update the demo-app.yaml file.

   cat > demo-app/demo-app.yaml << EOF
   apiVersion: smm.cisco.com/v1alpha1
   kind: DemoApplication
   metadata:
     name: smm-demo
     namespace: smm-demo
   spec:
     autoscaling:
       enabled: true
     controlPlaneRef:
       name: smm
     deployIstioResources: true
     deploySLOResources: true
     enabled: true
     enabledComponents:
     - frontpage
     - catalog
     - bookings
     - postgresql
     - payments
     - notifications
     - movies
     - analytics
     - database
     - mysql
     istio:
       revision: cp-v115x.istio-system
     load:
       enabled: true
       maxRPS: 30
       minRPS: 10
       swingPeriod: 1380000000000
     replicas: 1
     resources:
       limits:
         cpu: "2"
         memory: 192Mi
       requests:
         cpu: 40m
         memory: 64Mi
   EOF
   

3. Commit and push the changes to the Git repository.

   git add .
   
   git commit -m "upgrade demo-app to istio-cp-v115x"
   
   git push
   

4. Wait a few minutes, then check the IstioControlPlane of the demo-app.

   kubectl get ns smm-demo  -o=jsonpath='{.metadata.labels.istio\.io/rev}' --kubeconfig "${WORKLOAD_CLUSTER_1_KUBECONFIG}" --context "${WORKLOAD_CLUSTER_1_CONTEXT}" 
   

   Expected output: the demo-app is using the new istio-cp-v115x IstioControlPlane.

   cp-v115x.istio-system
   

5. Check the dashboard.

   • On the MENU > OVERVIEW page, everything should be fine.

     

   • On the MENU > MESH page, you can see both the old and the new IstioControlPlane, but both smm-controlplane and demo-app are using the new one.

     

   • Check the MENU > TOPOLOGY page.