Upgrades and Uninstall
Upgrading and uninstalling.
Upgrading
Each install is upgraded on its own, in Rancher (Apps → Installed Apps → ⋮ → Edit/Upgrade): pick the new chart version, keep the values, Upgrade. The Exchange and each department can upgrade on their own schedules. There is no upgrade script and no Agri Stack-wide version yet.
Commons Base, Commons Services
Each component's own Jobs and sanity checks run again
Commons Helm chart; the CM's sanity suite runs on every upgrade (CM deployment)
Crop Sown Registry
The seed runs again (idempotent); activity types, indicators and the ODK mapping are updated in place
Composite
The console's database Job (idempotent), its IAM registration and the sanity hook run again
Below
Composite.
Image versions: Image Tag and Console UI Image Tag. The chart's default
developmoves (pulled on every pod start); pin a released version in production.Use cases: a change to
composite.useCases(or your own ConfigMap) is picked up by running pods within the reload interval, without a restart or a chart upgrade.Registries and other settings are environment variables: changing them rolls the pods.
Signing key: kept on every upgrade (the chart reads its Secret back).
After a use case with new data scopes or purposes, each department decides whether to widen the Composite's scope policy (Releasing Registry Data to the Composite).
After any upgrade, check the Composite, the CMs and the registries' partner APIs together: run the test.
Upgrading an install from before the generated key. The Exchange questions of Commons Services moved under global.agriStackExchange (so Partner Management sees the role too). On the upgrade form, set Exchange Role again (and Exchange Domain where used): left at none, it overrides the earlier answer. Such an install keeps its Composite key and Partner Management entries; rotating it later: Keys: an older install.
Rotating keys: Keys.
Uninstalling
helm uninstall leaves databases, IAM rows and some Secrets behind. Use each product's script, with --dry-run first.
Composite
scripts/uninstall-agri-composite.sh --namespace <ns> [--release agri-composite] [--keep-db] [--keep-iam] [--drop-signing-secret] [--force] [--dry-run] [--yes]
Removes the release, leftover Jobs, and the ConfigMaps and Secrets labelled with the release; drops the console's database agri_composite and its role in commons-postgresql (unless --keep-db) and deletes the console's IAM rows (unless --keep-iam); the signing Secret only with --drop-signing-secret. Other options: --console-db, --console-db-user, --console-mnemonic, --iam-db, --postgres-release, --postgres-namespace, --signing-secret. --force runs while a Helm operation is in progress. Leaves the console's Keycloak client. No PVCs
Crop Sown Registry
scripts/uninstall-registry.sh --namespace <ns> [--release csr] [--keep-iam] [--keep-pvs] [--dry-run] [--yes]
Also drops the registry's database and role in commons-postgresql, its IAM rows, PVCs and their PVs (Uninstall)
Farmer Registry
scripts/uninstall-registry.sh --namespace <ns> --release fr [--keep-iam] [--keep-dashboards] [--dry-run] [--yes]
As above, and first removes the registry's Superset dashboards (its default release name is registry, so give --release fr)
None of the scripts touches Partner Management or the Consent Manager. The partners, their keys and their policies stay in Partner Management: in the Exchange, the Composite and the partners with their use-case policies; in each department, the Composite with its key and scope policies. If needed, disable the partners or revoke their policies there with a policy request (access policies).
Last updated
Was this helpful?