v7.0.0

Released: September 5, 2025

🚨 Upgrade Notices

• NeuVector 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.

  (root): Additional property cr is not allowed

  • It is possible that the new upstream values do not reconcile before the NeuVector Helm Release itself reconciles. This can cause NeuVector to default back from the EFS to an EBS backed volume, resulting in potential data loss. In order to prevent this, please suspend the NeuVector Helm Release before starting the upgrade.

    $ flux suspend hr neuvector -n bigbang
    ► suspending helmrelease neuvector in bigbang namespace
    ✔ helmrelease suspended

    Once you see the storageClass: efs-dynamic value reflected in the bigbang-neuvector-values secret as shown below during the upgrade, you can then resume the NeuVector Helm Release.

    $ kubectl get secret -n bigbang bigbang-neuvector-values -oyaml | yq '.data.overlays | @base64d | from_yaml | .upstream.controller.pvc'
    accessModes:
      - ReadWriteMany
    enabled: true
    storageClass: efs-dynamic
    $
    $ flux resume hr neuvector -n bigbang
    ► resuming helmrelease neuvector in bigbang namespace
    ✔ helmrelease resumed
    ◎ waiting for HelmRelease reconciliation
    ✔ HelmRelease neuvector reconciliation completed
    ✔ applied revision 2.8.6-bb.2

• Velero 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.

  (root): Additional property cr is not allowed

• Ensure that you manually remove any istio: and promtail: configuration from both the in-cluster overrides in the structsure-system namespace, as well as any external bigbang files you are passing in to Zarf. These have been deprecated (as mentioned in previous releases) and now removed by Big Bang.

  (root): Additional property promtail is not allowed
  (root): Additional property istio is not allowed

• SmoothGlue Console has been updated to Console Next. If SmoothGlue Console is enabled, it will be automatically upgraded to Console Next when upgrading to v7.0.0. This will result in the creation of a new database for Console Next (within the existing Console RDS instance if using SmoothGlue's IaC module) and migration of existing state to Console Next. To avoid upgrading to Console Next on an existing SmoothGlue instance, set the variable CONSOLE_LEGACY_MODE to true in your ZARF_CONFIG.
  • Console Next uses AuthService for authentication, so an AuthService chain must be created for the Console application as part of the migration. If the cluster has auto-SSO enabled, then this chain will be created automatically, but if not, then the AuthService chain and Keycloak client must be added manually as outlined in the Console Initial Setup Documentation.
• IaC: The Console RDS password will be cycled to change the hashing algorithm from md5 to scram-sha-256. This change will introduce some downtime for Console from the time the IaC is run until the package is deployed with the updated password.

📦 SmoothGlue Features

• Console Next has now been released as a part of SmoothGlue Enterprise! Console Next replaces the Legacy SmoothGlue Console and provides a familiar workflow to existing Console users, while providing an extensible framework for integration of new SmoothGlue features, such as Data Mesh.
• SmoothGlue’s Data Mesh has been released. Its capabilities include a Change Data Capture service and console features, enabling real-time database sync and built-in DDIL resilience.
• The SmoothGlue Keycloak theme has been updated. Styling has been updated for several pages, particularly the password update and OTP setup pages.

⏩ Upgraded Packages

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

🪲 Bug Fixes

• The default passwords automatically generated for NeuVector now match the minimum password strength requirements for the application.
• IaC: The mock inputs for the Velero module have been fixed.
• IaC: The allowed special characters for the Keycloak database password no longer include the hash (#) sign due to a Helm templating error.

❗️ Known Issues

• SonarQube automation for setting a randomized admin password is no longer functional for new SmoothGlue Build environments. This only affects new deployments of SmoothGlue Build. Environments that are upgrading from a previous version of SmoothGlue are unaffected.
• Jira Project Tool creation in Console results in an 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 and link to the organization user group.

🌐 Compatibility

• The packages for this release were built using Zarf v0.55.6.
• The packages were tested across the following Kubernetes distributions:
  • K3s: v1.33.4+k3s1
  • EKS: v1.31.11
• The following AMI versions were used for testing:
  • EKS AMI: smoothglue-eks-1.31.11-rocky-8-base-v1.1.1-stig-2025-09-01T08-22-28Z

🔗 Helpful Links

• Refer to the SmoothGlue documentation for additional guidance.
• For details on the Big Bang release, see the Big Bang Release Notes.