Skip to main content
Version: V2-Next

Updating

warning

Since this is the first version no stable update process is guaranteed.

This guide provides step-by-step instructions to help you upgrade your CORE installation.

General Update Process​

1. Backup your data​

Ensure your Backups are up to date and working.

Information on ways to back up the platform can be found in the Backups Guide.

2. Review the release notes​

  1. Check below for release notes and update instructions for all versions
  2. Pull the latest changes from the core repository or check out the specific version you want to update to.
  3. Look for changes in the defaults/environment/global.yaml file, as these may require adjustments in your custom configuration.
  4. If you changed any other default configuration files, check for changes in those files as well.
  5. If you changed helm values directly via rawValues, check for changes in the corresponding helm charts.

3. Update your deployment​

To see what will change between the current version and the new version you can use the helmfile diff command:

$ helmfile -f deployment/helmfile-instance.yaml.gotmpl -e <environment> diff

To update and approve all changes interactively, use the helmfile apply command:

$ helmfile -f deployment/helmfile-instance.yaml.gotmpl -e <environment> apply -i

Sometimes an update via "apply" might not be enough. For example when changes to the deployment were done manually in the cluster, or when the deployment requires more changes. In this case, you can use the helmfile sync command to sync all deployments with the helmfile configuration:

$ helmfile -f deployment/helmfile-instance.yaml.gotmpl -e <environment> sync

Multi-instance deployments​

If you run multiple instances on one cluster, remember the two-layer split when updating:

  • Instances are updated independently — run the commands above for each instance.
  • Shared operators are updated once per cluster with helmfile -f deployment/helmfile-operators.yaml sync -e <env>. An operator/CRD upgrade affects all instances simultaneously, so apply it before any instance starts using new custom-resource fields.

Version Specific Update Process​

Updating from CIVITAS/CORE v2.0.0 to v2.0.1​

warning

Before upgrading your installation, make sure you have backed up everything before you start the upgrade process. For production systems, we highly encourage to try an upgrade in a sandbox/test environment before.

1. Platform images update​

Change: The platform images authz-repo, config-adapter, nifiApache NiFiA stream processing and connector framework. In CIVITAS/CORE it is the pipeline engine for data integration and transformation (see ADR 047) and implements dataset-defined data flows.-extensions, backend-portal and frontend-portal where updated to version 1.3.1.

Action: No additional action is required. The updated images are installed when deploying CIVITAS/CORE v2.0.1.

2. Kyverno security update​

Change: Kyverno is updated to v1.19.2 and its Helm chart to 3.9.2.

Action: No additional action is required. If Kyverno is enabled, it is updated when deploying CIVITAS/CORE v2.0.1.

Updating from CIVITAS/CORE v2.0.1 to v2.0.2​

1. Security updates​

Change: Patch release for CVE-2026-114820 and other CVEs. The platform images are updated to version 1.3.2. KeycloakKeycloakAn open-source Identity and Access Management (IAM) solution providing SSO and OAuth2/OpenID Connect flows. In CIVITAS/CORE it is used to authenticate users and issue JWTs. is updated to 26.8.1-1. Superset, etcd and RabbitMQ get patch updates. NiFiApache NiFiA stream processing and connector framework. In CIVITAS/CORE it is the pipeline engine for data integration and transformation (see ADR 047) and implements dataset-defined data flows. gets the PostgreSQL JDBC driver from the nifiApache NiFiA stream processing and connector framework. In CIVITAS/CORE it is the pipeline engine for data integration and transformation (see ADR 047) and implements dataset-defined data flows.-extensions image and does not download it at start. The value postgresqlJdbcVersion is not used anymore.

Action: No additional action is required. The updated images are installed when deploying CIVITAS/CORE v2.0.2.