Upgrade

Read release notes before every upgrade. Authenticate to artifacts.altair.com and verify that the namespace-local registry secret remains available before changing a chart or image version.

Operators

Upgrade the operator chart, then apply CRD updates from approved release artifacts when required.

helm upgrade <operator-release> \
  oci://artifacts.altair.com/graph-helmoci/<operator-chart> \
  --version <operator-chart-version> \
  --namespace <namespace> \
  --values operator-values.yaml

Keep the image-pull secret in operator-values.yaml and in the product custom resource pod template. Operator manager secrets are not automatically inherited by Pods created for a custom resource.

Helm does not reliably upgrade CRDs. Check CRD instructions for the release.

Helm releases

Use direct Helm upgrade only when the chart release supports it:

helm upgrade <release-name> \
  oci://artifacts.altair.com/graph-helmoci/<chart> \
  --version <chart-version> \
  --namespace <namespace> \
  --values values.yaml

Retain the imagePullSecrets value in the upgrade values file so replacement Pods can authenticate to the Graph registry.

Graph Lakehouse data warning

warning

Graph Lakehouse persisted data can be incompatible across database versions, image changes, or cluster-shape changes such as vCPU count or node count. Some upgrade flows require azgctl -restart -init, which erases persisted data. Export or back up data first.

Before upgrading Graph Lakehouse:

1. Enable PVC retention.
2. Export or back up data.
3. Stop the database according to release instructions.
4. Apply the release-approved upgrade procedure.
5. Validate the database and reload data if required.