Upgrading Edge Delta

Upgrading the Edge Delta Pipeline.

  2 minute read  

The Edge Delta pipeline is abstracted from its configuration. A unique ID is used by each pipeline to communicate with the Edge Delta web app to populate your dashboard and retrieve its configuration. The Pipeline ID is passed in during installation.

This means you can upgrade a pipeline without changing its configuration. To upgrade, you pass the same Pipeline ID in while installing a more recent version.

To see installation instructions for a pipeline you want to upgrade:

To view the deployment commands for an existing v3 pipeline configuration:

  1. Click Pipelines and select the pipeline.
  2. Click Agents and select Upgrade Agents.

This example uses helm to upgrade. Replace the version v0.0.00 with the one you want to upgrade to, and replace the secretApiKey.value with the key associated with the pipeline’s configuration.

helm upgrade edgedelta edgedelta/edgedelta -i --version v0.0.00 --set secretApiKey.value=123456789 -n edgedelta --create-namespace

Agent Versions

Starting at version 0.1.71, Edge Delta agents use a Pipeline YAML file that has a config v3 structure, which enabled Visual Builder. In addition, v0.1.71 agents also support v2 configurations. You can’t downgrade a pipeline that uses a v3 configuration older than v0.1.71 without converting the configuration to v2.

Kubernetes Example

Suppose you have an existing pipeline on agent version 0.1.69 that is using the configuration Pipeline ID of 123456789. To upgrade to version 0.1.71:

  1. Update the Chart
helm repo update
  1. Run the deployment command provided by the Edge Delta application.
helm upgrade edgedelta edgedelta/edgedelta -i --version v0.1.71 --set secretApiKey.value=123456789 -n edgedelta --create-namespace

Clean Install

Occasionally, you need to do a clean installation by removing any existing Edge Delta pipelines and re-installing with the latest version. The agent release notes indicate which versions require a clean installation.

For kubernetes with Helm installations:

helm delete edgedelta -n edgedelta

Note: use the release name you specified and the namespace you specified when you installed the agent. The edgedelta release name and edgedelta namespace are the default values.

For Kubernetes with kubectl installations:

Note: The kubectl installation method is no longer supported. Please use Helm. If you require a manifest please generate one using Helm. Note: If an older manifest was used you can remove the entire namespace: kubectl delete namespace edgedelta

Some resources such as clusterrole and clusterrolebinding, which are not in the edgedelta namespace may remain. You can remove them as follows:

kubectl delete clusterrole edgedelta

kubectl delete clusterrolebinding edgedelta