Introduction
This guide explains how to update a Non-ISO NextGen Gateway from 22.x.x when container attestation is enabled. The procedure involves three stages: temporarily disable container attestation, update the gateway from the OpsRamp portal, and reenable container attestation after the update.
Applicability
Use this procedure only when both of the following conditions apply:
- The gateway uses a Non-ISO deployment and has the model number
ONGAPP. - Container attestation is enabled.
Note
This procedure is not required when container attestation is already disabled. Other upgrade prerequisites still apply. Do not use this procedure for ISO deployments or other gateway models.Check Container Attestation Status
Run the following command for the gateway’s namespace:
kubectl get pods -n <namespace>For example:
root@ubuntu:/home/ubuntu# kubectl get pods
NAME READY STATUS RESTARTS AGE
nextgen-gw-0 3/3 Running 0 3m15s
nextgen-gw-attestation-webhook-6f9b748594-8sbp9 1/1 Running 0 4m26s
nextgen-gw-attestation-webhook-6f9b748594-9mbbq 1/1 Running 0 4m26s
nextgen-gw-failover-watcher-6db868796f-mfvnk 1/1 Running 0 4m26s
nextgen-gw-redis-master-0 1/1 Running 0 4m26s
nextgen-gw-updater-cronjob-29915280-rj5b9 0/1 Completed 0 92m
webprobe-0 1/1 Running 0 19hIf the output shows container attestation pods, such as the nextgen-gw-attestation-webhook pods above, in the Running state, container attestation is enabled. Pod names and ages may differ.
You can also check the computed Helm values of the release:
helm get values nextgen-gw -n <namespace> --allCheck the global.containerAttestationEnabled value. For example, the relevant part of the output may look like this:
global:
containerAttestationEnabled: trueWhen this value is true, container attestation is enabled.
Known Issue
An update can fail when Helm runs using the gateway updater’s restricted ServiceAccount because the ServiceAccount cannot read cluster roles. The following error may appear in the updater log:
Error: UPGRADE FAILED:
clusterroles.rbac.authorization.k8s.io "nextgen-gw-attestation-vwc-default" is forbidden:
User "system:serviceaccount:default:nextgen-gw-updater-sa"
cannot get resource "clusterroles"
in API group "rbac.authorization.k8s.io" at the cluster scopePrerequisites
Before you begin, ensure that you have:
- A Kubernetes administrator who can run the Helm commands using credentials for the target cluster. The credentials must allow the administrator to manage the
nextgen-gwHelm release and its attestation-related cluster roles, cluster role bindings, and webhook configurations. - Helm and kubectl installed and configured for the target cluster, with access to the chart registry.
- Permission to start a gateway update in the OpsRamp portal.
- The gateway’s Kubernetes namespace and confirmed Helm release name. The following commands use
nextgen-gwas the release name. Replace<namespace>in every command with the gateway’s namespace.
Important
Do not run the Helm commands using the gateway updater’snextgen-gw-updater-sa ServiceAccount because it may not have the required cluster-level permissions.Step 1: Disable Container Attestation
List the Helm releases and record the currently installed chart version for
nextgen-gw:
Use only the chart version number forhelm list -n <namespace><chart-version>. For example, if the CHART column showsnextgen-gw-22.X.X, use22.X.X, not the full chart name or Helm revision.Disable container attestation using the same chart version. This step changes only the container attestation setting and does not change the gateway version:
helm upgrade nextgen-gw oci://us-central1-docker.pkg.dev/opsramp-registry/gateway-cluster-charts/nextgen-gw \ --version <chart-version> \ --set global.containerAttestationEnabled=false \ --reuse-values \ -n <namespace>Check the Helm release status and gateway workloads:
Continue only when Helm reportshelm status nextgen-gw -n <namespace> kubectl get pods -n <namespace>deployed, the gateway workloads are ready, and the administrator confirms that the attestation webhook configurations for this release have been removed.
Note
A successful Helm command alone does not confirm that all workloads are ready.Step 2: Update the Gateway
- Open the gateway in the OpsRamp portal and start the update to the target version confirmed by Support.
- Wait until the OpsRamp portal reports that the update is complete. Do not start another update while the current update is in progress.
- Confirm that the gateway is connected and healthy before proceeding.
Step 3: Reenable Container Attestation
List the Helm releases again and confirm that
nextgen-gwshows the expected target chart version:helm list -n <namespace>Reenable container attestation using the chart version installed after the update:
helm upgrade nextgen-gw oci://us-central1-docker.pkg.dev/opsramp-registry/gateway-cluster-charts/nextgen-gw \ --version <chart-version> \ --set global.containerAttestationEnabled=true \ --reuse-values \ -n <namespace>Check the Helm release status and workloads again:
Confirm that Helm reportshelm status nextgen-gw -n <namespace> kubectl get pods -n <namespace>deployed, the gateway and attestation workloads are ready, and the gateway remains connected in the OpsRamp portal.Have the administrator verify that the attestation webhook configurations and service endpoints are healthy and that attestation enforcement is restored before closing the maintenance window.