Skip to content
Latest (currently 2026.7.0) has the newest features, bug fixes, and CVE patches of Solo Enterprise for agentregistry.

Upgrade

Page as Markdown
Upgrade Solo Enterprise for agentregistry.
Before you begin

Review the changelogs for any breaking changes or new configuration that you want to use.
Upgrade

  1. Take a backup of the PostgreSQL database that your Solo Enterprise for agentregistry server is connected to. While Solo Enterprise for agentregistry does not delete data during a Helm upgrade, it is best practice to create a backup of your current data to account for any unexpected errors during the upgrade. In case the upgrade fails, you can safely restore a previous version of the product with your data.
    pg_dump --format=custom --no-owner \
 "postgres://${USER}:${PASSWORD}@${HOST}:5432/agentregistry?sslmode=disable" \
 > agentregistry-backup-$(date -u +%Y%m%dT%H%M%SZ).dump
    If you use the built-in PostgreSQL database instance, replace the placeholder values in this command with the following information:
    • $USER: agentregistry
    • $PASSWORD: agentregistry
    • $HOST: Port-forward the agentregistry-enterprise-postgresql-* service on your local machine and use localhost:PORT as the host value, or expose it as a LoadBalancer service and its address and port.
  2. If you have multiple replicas of the Solo Enterprise for agentregistry server, scale them down to 1.
    kubectl scale deploy/agentregistry-enterprise-server -n agentregistry-enterprise --replicas=1
  3. Set the version you want to upgrade to in an environment variable, such as the latest patch version (2026.7.0) .
    export NEW_VERSION=2026.7.0
  4. Get the Helm values file for your current version.
    helm get values agentregistry -n agentregistry-system -o yaml > values.yaml
open values.yaml
  5. Compare your current Helm chart values with the version that you want to upgrade to, and make any necessary changes.
    • Show all values:
      helm show values oci://us-docker.pkg.dev/solo-public/agentregistry-enterprise/helm/agentregistry-enterprise --version 2026.7.0
    • Get a file with all values: You can get a agentregistry-enterprise/values.yaml file for the upgrade version by pulling and inspecting the Helm chart locally.
      helm pull oci://us-docker.pkg.dev/solo-public/agentregistry-enterprise/helm/agentregistry-enterprise --version 2026.7.0
tar -xvf agentregistry-enterprise-2026.7.0.tgz
open agentregistry-enterprise/values.yaml
  6. Upgrade the Solo Enterprise for agentregistry Helm installation. Make sure to include your new Helm values either in the values.yaml file or with --set flags. Otherwise, any previous custom values that you set might be overwritten.
    In version 2026.6.0, the PostgreSQL database schema changed. During the upgrade of the Solo Enterprise for agentregistry server, your existing data is automatically copied from the old schema to the new schema. No configuration or Helm updates are required.

    You can choose to migrate your data before you upgrade the server so that the server starts on an already migrated database schema. To do that, use the arctl db migrate commands before you upgrade the Solo Enterprise for agentregistry Helm chart.
    helm upgrade -i -n agentregistry-system agentregistry oci://us-docker.pkg.dev/solo-public/agentregistry-enterprise/helm/agentregistry-enterprise \
  -f values.yaml \
  --version 2026.7.0
  7. Confirm that the control plane pods are up and running.
    kubectl get pods -n agentregistry-system
BYO PostgreSQL database