Rolling Software Update on Non-SMI Cluster

To configure the helm repository, use the following configuration:

  • Log in to cnSGW-C Ops Center and use the following configuration:

    config
     helm default-repository cn
     helm repository cn
     access-token smf-deployer.gen:AKCp5ekcX7DcBhuAmMZYfGLaHvH3E4Syr9TQDp1gjzcSjYrqsrGbXSYs5X2XYij3d9n9VfWQe
     url <old-build/new-build>
    exit

Validating the Update

The health check, current helm charts, and subscriber/peer/session information help in understanding whether the rolling update process is successful.

To validate the update, use the following steps:

  1. All pods that are deployed should be in the running state before and after an update.

    kubectl get pods -n cn
  2. Helm charts should reflect charts from the appropriate build.

    To check the helm charts currently deployed, use the following command in the cnSGW-C Ops Center.

    show helm charts
    show running-config helm repository
  3. Check subscriber, session, or peer information for retention validation, using the following configuration:

    show subscriber namespace sgw count all
    show peers all