How to externally upgrade your Edge site

With External upgrade mode, a new version of your Edge site is applied through your own tooling, outside of Edge's Automatic or Manual upgrade flow. How you upgrade depends on how you installed your Edge site.

Note You don't need to set the External upgrade mode manually. Edge sets it automatically when you upgrade your Edge site externally.

Upgrade your Edge sites via a CD tool (Argo CD example)

If you installed your Edge site using a CD tool, you manage every step of the installation yourself, including upgrades.

The following is an example of how to upgrade your Edge site with Argo CD by running helm and kubectl commands directly against your cluster. If a continuous delivery (CD) tool manages your release, update the version it targets instead, as shown in step 3.

Note  You must be familiar with your organization's CD tool and Helm to upgrade your site via a CD tool.

Prerequisites

Steps

  1. Find the version you want to upgrade to. Query the Edge REST API for the versions available to your site:
    Copy
    GET /rest/edge/v1/sites/{siteId}/versions
    Note Replace {siteId} with your Edge site ID, and authenticate with your Collibra credentials. For the full request and response reference, go to List available upgrade versions for a site in the Collibra Developer Portal.
  2. Change the chart version that the Argo CD Application targets. Replace <new-exact-version> with the exact chart version string. Automated sync applies the change.
    Copy
    kubectl patch application collibra-edge -n argocd --type merge \
      -p '{"spec":{"source":{"targetRevision":"<new-exact-version>"}}}'

    To roll back, run the following command. Replace <HISTORY_ID> with the history ID of the version to roll back to.

    Copy
    argocd app rollback collibra-edge <HISTORY_ID>
    Note Argo CD doesn't resolve pre-production builds from a version range, so use the exact version string.

What's next?