Upgrading Dash Enterprise

Your organization is responsible for performing Dash Enterprise upgrades. We’ll notify you when a new version is available.

To ensure you remain eligible for support, upgrade Dash Enterprise regularly. We recommend keeping your instance as close to the latest version as possible for best results.

Contact us for upgrade help.

Checking the Current Version

helm ls --all-namespaces

Next to the namespace for the Dash Enterprise instance whose version you want to check, look at the CHART or APP VERSION.

Before Upgrading

Before upgrading Dash Enterprise, we strongly recommend carefully reading the changelog for the version that you want to upgrade to, as well as any intermediate versions.

Follow one or many of the upgrade procedures below corresponding to your current and target versions.

6.1.X to 6.2.2

Prerequisites

• kubectl access to the cluster
• Helm v3.14 or later
• If performing the upgrade from an internet-restricted machine, then you have obtained the bundle of Dash Enterprise images for the version that you are upgrading to and you have pushed it to your private container registry.
• Make sure that the following variables are defined in your environment (note that the CHART_VERSION differs from what you set during your installation):
  txt export CHART_VERSION=6.2.2 export RELEASE_CHANNEL=standard export CHART_REGISTRY=oci://registry.replicated.com/dash-enterprise export RELEASE_NAME=dash-enterprise export NAMESPACE=<your-namespace> export LICENSE_ID=<license-id> export EMAIL=<email>
  If installing from an image bundle that is already pushed to your private container registry, then you also need export SKIP_PUSH=1.

Upgrade Notices

Make sure you’re aware of the following when passing through the intermediate versions below:

• [6.2.1] Important: Upgrading causes all apps and workspaces to restart.

• [6.2.0] User-created workloads now use a read-only filesystem by default. If any apps or workspaces need to write to the filesystem (such as for running predeploy or postdeploy scripts), an allowWritableRootFs: true configuration change is needed. The overrides below allow apps and workspaces to use sudo and write to the filesystem:

• For apps:
  yml agents: worker: app: allowPrivilegeEscalation: true allowWritableRootFs: true capabilities: add: - SETUID - SETGID - AUDIT_WRITE

• For workspaces:
  yml agents: worker: workspace: allowPrivilegeEscalation: true allowWritableRootFs: true capabilities: add: - SETUID - SETGID - AUDIT_WRITE

• [6.2.0] Build resource configuration: agents.build.builder.resources is no longer used. Migrate to per-container keys if you were previously using it in your configuration override: agents.build.builder.lifecycle-build.resources, agents.build.builder.lifecycle-export.resources, and agents.build.builder.logging-sidecar.resources.

Running the Upgrade

To upgrade Dash Enterprise from 6.1.X to 6.2.2:

1. Authenticate to the Replicated registry if you aren’t already:
   sh echo $LICENSE_ID | helm registry login registry.replicated.com \ --username "$EMAIL" \ --password-stdin

2. Use one of the following commands:

• If you don’t need to apply a configuration override:
  sh helm upgrade $RELEASE_NAME \ $CHART_REGISTRY/$RELEASE_CHANNEL/dash-enterprise \ --version "$CHART_VERSION" \ --namespace $NAMESPACE \ --reset-then-reuse-values

• If you need to apply a configuration override:
  sh helm upgrade $RELEASE_NAME -f custom-values.yaml \ $CHART_REGISTRY/$RELEASE_CHANNEL/dash-enterprise \ --version "$CHART_VERSION" \ --namespace $NAMESPACE \ --reset-then-reuse-values
  changing the name of your custom values file if it is different.

  (the --reset-then-reuse-values flag applies all configuration settings that you applied during the original installation and that are not modified in this command).

6.0.X to 6.1.0

Prerequisites

• kubectl access to the cluster
• Helm v3.14 or later
• If performing the upgrade from an internet-restricted machine, then you have obtained the bundle of Dash Enterprise images for the version that you are upgrading to and you have pushed it to your private container registry.
• Make sure that the following variables are defined in your environment (note that the CHART_VERSION differs from what you set during your installation):
  txt export CHART_VERSION=6.1.0 export RELEASE_CHANNEL=standard export CHART_REGISTRY=oci://registry.replicated.com/dash-enterprise export RELEASE_NAME=dash-enterprise export NAMESPACE=<your-namespace> export LICENSE_ID=<license-id> export EMAIL=<email>
  If installing from an image bundle that is already pushed to your private container registry, then you also need export SKIP_PUSH=1.

Upgrade Notices

• auth.keycloak.internalCaSecretName is deprecated in Dash Enterprise 6.1.0. See more information in the changelog.

Running the Upgrade

To upgrade Dash Enterprise from 6.0.X to 6.1.0:

1. Authenticate to the Replicated registry if you aren’t already:
   sh echo $LICENSE_ID | helm registry login registry.replicated.com \ --username "$EMAIL" \ --password-stdin

2. If you are affected by the auth.keycloak.internalCaSecretName deprecation, create a ConfigMap for your self-signed or internal CA certificate:
   sh CA_CONFIGMAP_NAME=keycloak-ca-cert kubectl create configmap $CA_CONFIGMAP_NAME \ --namespace=$NAMESPACE \ --from-file="$KEYCLOAK_CA_CERT" \ --dry-run=client -o yaml | kubectl apply -f -

3. Run one of the following commands:
   * If you are not affected by the auth.keycloak.internalCaSecretName deprecation:
   sh helm upgrade $RELEASE_NAME \ $CHART_REGISTRY/$RELEASE_CHANNEL/dash-enterprise \ --version "$CHART_VERSION" \ --namespace $NAMESPACE \ --reset-then-reuse-values
   (the --reset-then-reuse-values flag applies all configuration settings that you applied during the original installation and that are not modified in this command).

• If you are affected by the auth.keycloak.internalCaSecretName deprecation:
  sh helm upgrade $RELEASE_NAME \ $CHART_REGISTRY/$RELEASE_CHANNEL/dash-enterprise \ --version "$CHART_VERSION" \ --namespace $NAMESPACE \ --set auth.keycloak.internalCaCertConfigMapName=keycloak-ca-secret \ --reset-then-reuse-values
  (the --reset-then-reuse-values flag applies all configuration settings that you applied during the original installation and that are not modified in this command).