Upgrading with Streaming and Governance Charts

Changes in version 2025.3

General prerequisites

Before you upgrade to 2025.3, please make sure:

  • You are performing the deployment with any of the following Axual Streaming 2025.2 versions

    • Axual Streaming Charts 1.3.x series

  • You are performing the deployment with any of the following Axual Governance 2025.2 versions

    • Axual Governance Charts 1.1.x series

  • You are running kubernetes version 1.24.x or later

  • You are not overriding any components' versions (search for tag: overrides in your values.yaml)

You can upgrade each part of the Axual Platform independently, we suggest starting from the Streaming and then move to the Governance.

Governance Prerequisites

  • Be sure to have set the connectionCollation=utf8mb4_unicode_ci parameter to the Platform Manager’s spring.datasource.url to connect to a mariadb or mysql database

platform-manager:
  config:
    spring:
      datasource:
        url: "[YOUR_EXISTING_JDBC_URL]&connectionCollation=utf8mb4_unicode_ci"

Performing the upgrade

Upgrade Axual Streaming to 1.4.0

Start with Axual Streaming 2025.2 being installed using Axual Streaming Charts of the 1.3.x series.

Use the general upgrade steps for upgrading best-practice.

  1. Update the Axual helm repository to download the latest charts available

    helm repo update

  2. Upgrade the Axual Streaming installation

    helm upgrade --install streaming oci://registry.axual.io/axual-charts/axual-streaming --version=1.4.0 -n kafka

This command will restart all streaming pods.

Once restarted, verify everything is running fine before considering the upgrade done.

Axual Governance Charts

Start from Axual Governance 2025.2 installed using Axual Governance Charts series 1.1.x.

Use the general upgrade steps for upgrading best-practice.

  1. Update the Axual helm repository to download the latest charts available

    helm repo update

  2. Upgrade the Axual Governance installation

    helm upgrade --install governance oci://registry.axual.io/axual-charts/axual-governance --version=1.2.0 -n kafka

This command will restart all governance pods.

Once restarted, verify everything is running fine before considering the upgrade done.

You can follow the Post upgrade section to enable new features.

Post upgrade

To run KSML 1.1.0 with all features available, you need to do the following:

  • Configure the available Kafka bootstrap endpoints for each cluster via the Kafka Authentications, this allow the KSML application to run with the correct Kafka bootstrap endpoint based on the configuration application authentication.

  • Configure the Schema Registry endpoints (e.g., Apicurio, Confluent) for each KSML Provisioner, which are automatically passed to all KSML applications started with that KSML Provisioner.

  • Configure your KSML Provisioner deployment with available KSML notations, these notations will be then used by any of your KSML definition.

# KSML Runner Configuration
ksmlRunnerConfig:
  # -- KSML Notations
  notations:
    avro:
      type: confluent_avro
      schemaRegistry: confluent
      config:
        normalize.schemas: true
        auto.register.schemas: false

    protobuf:
      type: apicurio_protobuf
      schemaRegistry: apicurio
      config:
        apicurio.registry.auto-register: true
        apicurio.registry.auto-register.if-exists: "RETURN"

    jsonschema:
      type: apicurio_jsonschema
      schemaRegistry: apicurio
      config:
        apicurio.registry.auto-register: true
        apicurio.registry.auto-register.if-exists: "RETURN"

Once all the above steps are completed, you can use the new features.