Skip to main content
SmoothGlue Logo
In this section

v6.21.0

Released: August 8, 2025

6.21.0 (2025-08-08)​

🚨 Upgrade Notices​

Big Bang Upstream Passthrough Pattern​

This release includes four new packages that are being migrated to the upstream passthrough pattern. The affected packages are keycloak, argocd, fluentbit, gitlabRunner and sonarqube.

Please carefully review the Big Bang 3.3.1 Release Notes to ensure values are migrated properly.

Example values before:

fluentbit:
  values:
    testFramework:
      enabled: false

addons:
  argocd:
    values:
      configs:
        cm: 
          oidc.config: |
            name: keycloak

  keycloak:
    values:
      resources:
        requests:
          cpu: "1"
          memory: "1Gi"
        limits:
          memory: "1Gi"

  sonarqube:
    values:
      sonarProperties:
         sonar.core.serverBaseURL: "https://your.sonarqube.url/" 

  gitlabRunner:
    values:
      resources:
        limits:
          cpu: 500m
          memory: 750Mi
        requests:
          cpu: 200m
          memory: 256Mi

Example values after applying upstream passthrough pattern:

fluentbit:
  values:
    upstream:
      testFramework:
        enabled: false

addons:
  argocd:
    values:
      upstream:
        configs:
          cm: 
            oidc.config: |
              name: keycloak
    
  keycloak:
    values:
      upstream:
        resources:
          requests:
            cpu: "1"
            memory: "1Gi"
          limits:
            memory: "1Gi"

  sonarqube:
    values:
      upstream:
        sonarProperties:
          sonar.core.serverBaseURL: "https://your.sonarqube.url/" 

  gitlabRunner:
    values:
      upstream:
        resources:
          limits:
            cpu: 500m
            memory: 750Mi
          requests:
            cpu: 200m
            memory: 256Mi

SonarQube​

❗️ This update includes several breaking changes. Please read these notices carefully.

Upgrade Steps to Prevent Data Loss

This release includes a major refactor of the upstream SonarQube Helm chart, which changes how the PostgreSQL dependency and StatefulSets are managed. Due to these changes, a conflict can occur with the PostgreSQL secret and StatefulSets created by previous versions of this chart, which can cause the upgrade to fail. The serviceName of the PostgreSQL StatefulSet has changed from sonarqube-postgresql to sonarqube-postgresql-headless, which is an immutable field. To perform a successful upgrade while preserving your existing SonarQube data, you must delete the old secret and StatefulSets, and then perform the upgrade.

Follow these steps to upgrade your SonarQube instance:

  1. Backup your database prior to performing any upgrades.

  2. Suspend the helm release:

    flux -n bigbang suspend helmrelease sonarqube

  3. Delete the old PostgreSQL secret to prevent the upgrade from failing due to a secret conflict:

    kubectl delete secret sonarqube-postgresql -n sonarqube

  4. Delete the existing StatefulSets to prevent the upgrade from failing due to immutable field errors:

    kubectl delete statefulset sonarqube-postgresql sonarqube-sonarqube -n sonarqube

  5. Upgrade SmoothGlue: Perform your SmoothGlue upgrade.

  6. Wait for the Big Bang helm release to report it has successfully reconciled to version 3.3.1.

  7. Resume the helm release: This may not complete until all the next steps are done:

    flux -n bigbang resume helmrelease sonarqube

  8. Verify Pod and Helm Release: The sonarqube-sonarqube-0 pod should be Running; the helm release will remain a READY state of Unknown:

    kubectl -n sonarqube get pods; kubectl -n bigbang get helmrelease sonarqube

  9. Navigate to your SonarQube site. It will probably display SonarQube is under maintenance.

  10. Follow the SonarQube Upgrade Roadmap: https://docs.sonarsource.com/sonarqube-community-build/server-upgrade-and-maintenance/upgrade/roadmap/. You will likely need to navigate to https://yourSonarQubeURL/setup and follow the instructions.

  11. Verify Helm Release: The SonarQube helm release should show Ready: True:

    kubectl -n bigbang get helmrelease sonarqube

  12. If SSO is configured, validate that it is still functional. If receiving a 500 error with a similar log from the pod as indicated in this upstream thread, please log in as the admin account, remove the SSO config, and restart the pod to resolve the error.

⏩ Upgraded Packages​

  • Confluence: chart bump: 2.0.2-bb.5
  • Jira: chart bump: 2.0.2-bb.1
  • Big Bang 3.3.1

❗️ 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.

🌐 Compatibility​

  • The packages for this release were built using Zarf v0.55.6.
  • The packages were tested across the following Kubernetes distributions:
    • RKE2: v1.31.8+rke2r1
    • K3s: v1.32.5+k3s1
    • EKS: v1.31.7
  • The following AMI versions were used for testing:
    • RKE2 AMI: smoothglue-rke2-v1.31.8-rke2r1-rocky-8-base-v1.1.1-stig-2025-05-19T08-22-30Z
    • EKS AMI: smoothglue-eks-1.31.7-rocky-8-base-v1.1.1-stig-2025-07-21T08-24-21Z

🔗 Helpful Links​