Upgrade
Plan Governance Platform upgrades as customer operations. Review the release manifest, release notes, known issues, and rollback plan before changing a running environment.
Before Upgrade
Section titled “Before Upgrade”- Confirm the target release supports the customer Kubernetes version and architecture.
- Back up PostgreSQL, object storage, chart values, and platform secrets according to customer policy.
- Review migration notes and behavior changes.
- Confirm identity provider, storage, key-management, and registry access are healthy.
- Pause non-essential bulk workflows if the customer rollout plan requires it.
Upgrade Flow
Section titled “Upgrade Flow”Upgrade the Governance Platform chart to the version recorded in the release manifest, using reviewed customer values and secrets.
After the upgrade, verify service readiness, sign-in, project access, attachments, reports, indicators, lineage, and certificate workflows.
After Upgrade
Section titled “After Upgrade”Record the upgraded chart version, values revision, release manifest, validation evidence, and any customer-visible issues. Keep rollback artifacts available until the customer accepts the upgrade.