​

Upgrading from 0.3 to 0.4

1. Use the new values file. The 0.4 file turns on notification-service (governance notices and alerts depend on it), ClickHouse (monitors, alerts, LLM traffic figures and agent telemetry depend on it) and agent telemetry. With the 0.3.3 file the upgrade succeeds, but those features quietly do nothing.
2. Tell the relay where your agents are. If your agents or MCP servers run in your cluster or on a private network, list them in services.relay.ssrfAllowedHosts. Details.
3. Plan for 12 GiB. Three new pods (swarmd-notification, swarmd-clickhouse, swarmd-telemetry) take memory requests to about 6 GiB, plus a 20 GiB ClickHouse volume.
4. A rollback to 0.3.3 needs a database restore. Details.

​

What is new

​

A redesigned platform UI

• Ctrl/Cmd-K opens “Go to page” from anywhere.
• Directories open beside the list. Selecting an agent, MCP server, gateway, provider, user, group, channel or sign-in provider opens its full workspace next to the directory. A direct link still opens the full page, and old ?inspect= links redirect.
• One status filter, with counts, on every directory.
• Compact mode: a toggle in the app bar for denser workspaces. It is remembered per browser.
• Immutable proof (Govern) shows hash-chain status and lets you verify it.
• Policy bindings (Govern) shows where each policy applies, including what is inherited, and lets you reorder.
• Trace explorer has a split inspector with a single breakdown timeline.
• Manage › Notifications has Channels and Destinations tabs. The old Overview tab is gone.
• Edit and delete controls now follow the exact permission the API enforces. ADMIN on its own no longer shows WRITE or DELETE controls. A custom group that relied on that needs WRITE/DELETE granted explicitly; the API never accepted those calls anyway.

​

AI governance (EU AI Act)

​

Art. 50 transparency

​

Evaluation sets run for real

• Target agents really execute when you run a set.
• A hop that could not complete is Error, not Failed.
• Disabled evaluations show as Skipped.
• Rate limits stand aside for evaluation runs, so runs do not use your tenant’s budget.
• Only the first (entry) hop of a chain can be asserted reliably for now.

​

LLM gateway and provider traffic

​

Agent telemetry (preview)

​

Notifications

​

Smaller changes

• Clearer relay refusals. A message to a deregistered or frozen agent now says so, instead of “Not authorized”. If anything of yours matches on that error text, check it.
• Sign-in and sign-out. Sign-out always lands on the login page, a signed-in user who opens /login goes straight on, and SSO no longer needs a second attempt after an expired session. The login button cannot be submitted twice.
• Python SDK 0.4. LOG_LEVEL now sets the root logger’s level, so your agents’ own logger.info() lines appear. Agent telemetry support has been added (off by default).

​

Security

• Credentials at rest use your install’s key. The platform encrypts the credentials it stores: LLM provider keys, the API keys, bearer tokens and OAuth client secrets you give it for calling agents and MCP servers, MCP OAuth tokens, and agent webhook secrets. On 0.3.x installs from this chart they were encrypted with a built-in default key instead of the key generated for your install. From 0.4.1 everything new is encrypted with your install’s key, and existing values still decrypt. Re-save stored credentials after upgrading (see After the upgrade) so they are re-encrypted with it.
• Service accounts have their own secrets. Each platform service’s Keycloak client now gets a secret generated for your install, replacing a built-in default. This is applied automatically during the upgrade.
• Agents and services carry the audience the platform checks. On 0.3.x installs from this chart, agent tokens and some service-to-service tokens lacked the audience that registry and relay require, so agents calling the platform API were refused. Existing agents and channels are fixed automatically when registry starts.
• Session isolation in the web UI. Concurrent token refreshes could, in a narrow race, hand one signed-in user another user’s session. The refresh lock is now per refresh token. Upgrade every platform-ui replica; we also recommend asking users to sign in again after the upgrade.
• Image pulls are scoped. Licence-issued registry credentials can now pull only released images and charts. Installs from a release tarball are not affected.

​

Before you upgrade

NS=swarmd
PGUSER=$(kubectl -n $NS get secret swarmd-generated-credentials -o jsonpath='{.data.postgres-username}' | base64 -d)
PGPASS=$(kubectl -n $NS get secret swarmd-generated-credentials -o jsonpath='{.data.postgres-password}' | base64 -d)

for db in swarmd keycloak; do
  kubectl -n $NS exec deploy/swarmd-postgres -- \
    env PGPASSWORD="$PGPASS" pg_dump -U "$PGUSER" -Fc "$db" > "$db-0.3.3.dump"
done
ls -lh *.dump   # both files should be non-empty

kubectl -n swarmd get secret swarmd-generated-credentials -o json \
  | jq '{"encryption-key": .data["encryption-key"], "audit-hashchain-signing-key": .data["audit-hashchain-signing-key"]}' \
  > swarmd-keys-0.3.3.json

diff my-0.3.3-values.yaml values-prismforce-local.yaml

services:
  relay:
    ssrfAllowedHosts: "*.prismforce-agents.svc.cluster.local,crm-mcp.corp.internal"

helm diff upgrade swarmd ./swarmd-0.4.1.tgz -n swarmd -f values-prismforce-local.yaml

​

Upgrade

helm upgrade swarmd ./swarmd-0.4.1.tgz -n swarmd \
  -f values-prismforce-local.yaml \
  --wait --timeout 15m

​

Schema changes in this release

​

After the upgrade

helm -n swarmd list                 # chart swarmd-0.4.1
kubectl -n swarmd get pods          # all Running, 1/1, RESTARTS 0 — including notification, clickhouse, telemetry
kubectl -n swarmd logs deploy/swarmd-registry | grep -i 'Successfully applied\|up to date'

​

Rolling back

helm rollback swarmd -n swarmd --wait --timeout 15m
# then restore the dumps you took before upgrading
kubectl -n swarmd scale deploy -l app.kubernetes.io/instance=swarmd --replicas=0
kubectl -n swarmd scale deploy/swarmd-postgres --replicas=1
for db in swarmd keycloak; do
  kubectl -n swarmd exec -i deploy/swarmd-postgres -- \
    env PGPASSWORD="$PGPASS" pg_restore -U "$PGUSER" --clean --if-exists -d "$db" < "$db-0.3.3.dump"
done
kubectl -n swarmd scale deploy -l app.kubernetes.io/instance=swarmd --replicas=1

​

Next