Skip to main content
SmoothGlue Logo
In this section

v7.3.0

Released: October 16, 2025

🚨 Upgrade Notices​

  • This release will force the Aurora PostgreSQL upgrade to from 13.x -> 14.x for the apps listed below.
    • Jira
    • Console
    • Keycloak
    • Mattermost
    • Sonarqube
  • The two variables allow_major_version_upgrade and apply_immediately have been set to true by default. The rds_engine_versionvariable is now set to 14 by default. To opt out of the immediate upgrade, set the variable flag apply_immediately to false and the upgrade will happen during the scheduled maintenance window. To opt out of the Aurora upgrade entirely, set the allow_major_version_upgrade flag to false and set the rds_engine_version back to 13 as shown in the example below.

Example env.hcl

locals {
  jira_inputs = {
    rds_engine_version = 13
    apply_immediately = false
    allow_major_version_upgrade = false
  }
  console_inputs = {
    rds_engine_version = 13
    apply_immediately = false
    allow_major_version_upgrade = false
  }
  keycloak_inputs = {
    rds_engine_version = 13
    apply_immediately = false
    allow_major_version_upgrade = false
  }
  mattermost_inputs = {
    rds_engine_version = 13
    apply_immediately = false
    allow_major_version_upgrade = false
  }
  sonarqube_inputs = {
    rds_engine_version = 13
    apply_immediately = false
    allow_major_version_upgrade = false
  }
}
  • Console now requires enabling integrations when providing an access token for that application. If Console is configured with an access token for one of its supported integrations, please provide the following additional config to ensure the integration is still enabled:
  packages:
    console:
      values:
        backend:
          mattermost:
            enabled: true
            accessToken: <ACCESS_TOKEN>
          gitlab:
            enabled: true
            accessToken: <ACCESS_TOKEN>
          jira:
            enabled: true
            accessToken: <ACCESS_TOKEN>
  • Sonarqube requires a manual database upgrade on existing clusters. Complete a full backup of the Sonarqube database before applying the upgrade. After applying the upgrade, navigate to <SonarqubeURL>/setup and follow the prompts in the UI to upgrade the database. Additional information can be found here.
  • Grafana:
    • Passthrough Refactor: The grafana chart has been refactored to the Big Bang "passthrough" chart pattern - please read this upgrade notice is its entirety. All upstream chart value overrides in ./chart/values.yaml will need to be shifted under the upstream key. If you do not migrate the values, you will see an error similar to the following on the HelmRelease.
  (root): Additional property cr is not allowed.
  • Minio now enforces schema validation for provided Helm values; ensure that any package-specific values have been migrated under the upstream key,  as described in the Big Bang Passthrough Documentation. If you do not migrate the values, you will see an error similar to the following on the HelmRelease.
  (root): Additional property cr is not allowed.
  • Minio Operator now enforces schema validation for provided Helm values; ensure that any package-specific values have been migrated under the upstream key,  as described in the Big Bang Passthrough Documentation. If you do not migrate the values, you will see an error similar to the following on the HelmRelease.
  (root): Additional property cr is not allowed.

📦 SmoothGlue Features​

  • This release of SmoothGlue Enterprise v7.3.0 includes Big Bang Version 3.8.0. For more details on the features and updates included in Big Bang Version 3.8.0, please refer to the Big Bang Release Notes.

⏩ Upgraded Packages​

  • Jira from 10.3.9 to 10.3.11
    • miniOrange has been updated (users are responsible for updating this).
  • SmoothGlue Datamesh from v0.1.1 to v0.1.2.

🐞 Bug Fixes​

  • Loki: If you were running Loki in single binary (monolith) mode (the default setting); it will now automatically be re-configured to run in scalable mode (which is recommended for production workloads). Loki will also start logging to the relevant s3 buckets created.

❗ Known Issues​

  • Jira Project Tool creation in Console results in error message.
An error occurred: Exception while creating project Tool: 400 Client Error: Bad Request for url:

The workaround is to manually create the project in Jira linked to the organization user group.

🌐 Compatibility​

  • The packages for this release were built using Zarf v0.62.0.
  • The packages were tested across the following Kubernetes distributions:
    • RKE2: v1.31.13+rke2r1
    • K3s: v1.34.1+k3s1
    • EKS: v1.31.13
  • The following AMI versions were used for testing:
    • RKE2 AMI: smoothglue-rke2-v1.31.13-rke2r1-rocky-8-base-v1.1.1-stig-2025-09-29T08-26-24Z
    • EKS AMI: smoothglue-eks-1.31.13-rocky-8-base-v1.1.1-stig-2025-09-29T08-26-32Z
    • Base AMI: base-Rocky-8-EC2-LVM-v1.1.1-stig-2025-09-29T0704