Skip to content

How to update the Keycloak Package chart📜

Big Bang makes modifications to the upstream Codecentric helm chart. The upstream Keycloak image from IronBank is used in conjuction with a custom Keycloak plugin. The custom P1 plugin contains custom authz and authn code, custom self-registration theme, and automatic joining of groups based on certian registration information like the use of a DoD CAC. The plugin code is hosted at Platform One custom plugin artifact image is hosted in Iron Bank at

Note: Be aware that there are currently two versions of Keycloak. One is the legacy version that uses Wildfly for the application server. The other version is the new one using Quarkus. Big Bang has migrated to the new Quarkus version. The images in Iron Bank have tag without the “legacy” X.X.X.

  1. Read Release Notes: from the upstream Keycloak documentation. Carefully review the release notes for the new Keycloak version to understand any breaking changes or required manual upgrade steps.

  2. Identify Chart Changes: Perform a diff between the current and upstream charts to identify significant changes.

  3. Merge Chart Updates: Manually merge the new chart updates into the existing Keycloak package code, paying close attention to Big Bang-specific modifications. See the Modifications made to upstream chart section below.

  4. Update Chart Files: Update the chart/Kptfile with the new chart version and commit hash.

  5. Update Add an entry describing the upgrade, including the new Keycloak and chart versions.

  6. Update Chart.yaml: Update the chart/Chart.yaml file with the appropriate versions for Keycloak, dependencies, and annotations.

    version: XX.X.X-bb.X
    appVersion: XX.X.X-legacy
      - name: gluon
        version: "X.X.X"
    annotations: |
        - Keycloak: XX.X.X |
        - name: keycloak
        - name: postgreslXX
        condition: postgresql.enabled
        - name: base
        condition: bbtests.enabled

  7. Update Update the file following the gluon library script guidelines noting any additional chart changes you make during development testing.

  8. Run Helm Dependency Update: Execute helm dependency update ./chart to update the chart archives and generate a new requirements.lock file. Commit both the archives and the lock file.

    helm dependency update ./chart

  9. Build and Publish Plugin Image: Follow the instructions in the P1 plugin repository to build and publish a new plugin image to the IronBank container registry. Use a test label for the image initially.

  10. Test Keycloak and Plugin: Conduct thorough testing of Keycloak, the custom plugin, and end-to-end SSO using a full k8s deployment. Refer to the Testing with custom P1 plugin section for detailed instructions.

    • Test the admin console
    • Test the custom user forms
    • Test registering a user with a CAC verifying that the user is automatically added to the IL2 group.
    • Test logging in from the account page.
    • Test registering a regular user with username and password.
    • Test login at the account page with OTP.
  11. Update Documentation: After successful testing, update all documentation with the new Keycloak and plugin versions.

  12. Create Release Tag: Create an official semver release tag in the P1 plugin repository and monitor the mirrored Party Bus IL2 pipeline for successful completion.

  13. Publish Official Plugin Image: Publish the official plugin image to IronBank, following the provided instructions.

  14. Update BigBang MR: Update the tests/test-values.yaml file in the BigBang MR with the new plugin init-container tag, using either the test image or the official IronBank image.

Testing with custom P1 plugin📜

  1. Create k8s Dev Environment: Use the Big Bang script with the -a option to create a k3d cluster with metalLB and a passthrough gateway for Keycloak.

  2. Deploy Big Bang: Deploy Big Bang with Istio-operator, Istio, Gitlab, Sonarqube, and Mattermost enabled. Ensure SSO is enabled for Gitlab and Sonarqube, but not for Mattermost initially. Use the provided example Big Bang values override file and modify the plugin image label to use your test image.

    helm upgrade -i bigbang ./chart \
        -n bigbang --create-namespace \
        -f ../overrides/keycloak-bigbang-values.yaml \
        -f ../overrides/registry-values.yaml \
        -f ./chart/ingress-certs.yaml
  3. Register Test Users: Create two test users in Keycloak, one with a CAC and one without (username/password/OTP). Note: You may create these test users through the admin UI, but must also create them in the baby-yoda realm and add them to the IL2 Users group.

  4. Test Admin Console: Access the Keycloak admin console using the default credentials (admin/password) and verify functionality.

  5. Test End-to-End SSO: Test SSO with Gitlab and Sonarqube for both CAC and non-CAC users. Update the sso.saml.metadata value in your override file for Sonarqube testing.

  6. Test Mattermost: Create a user in Mattermost with username/password and then attempt to log in using the Gitlab OIDC link.

    • Browse to and create a user with username/password. This option should be available if addons.mattermost.sso.enable_sign_up_with_email is enabled. This test simply validates that normal authentication works when SSO is not forced.
    • After you have logged in, log out and attempt to create an SSO user using the Gitlab OIDC link. Once you finish authenticating, you should return to mattermost as expected and be logged in as your keycloak user.
  7. Test Custom User Forms: Verify the functionality of the custom user forms for account management.


Note: Occasionally the DoD certificate authorities will need to be updated. Follow the instructions at /scripts/certs/ and copy the new truststore.jks to ./chart/resources/dev and to]( . You may need to edit /scripts/certs/ to update to the most recent published certs but it usually points to the latest archive.

Modifications made to upstream chart📜

This is a high-level list of modifications that Big Bang has made to the upstream helm chart. You can use this as as cross-check to make sure that no modifications were lost during the upgrade process.


  • disable all internal services other than postgres
  • add BigBang additional values at bottom of values.yaml
  • add IronBank hardened image
  • Add IronBank postgresql12 image for dev/CI development/testing
  • and other miscellaneous change. Diff with previous version to find all changes
  • modify pgchecker image to ironbank postgres image


  • run helm dependency update and commit the downloaded archives
  • also commit the requirements.lock file so that air-gap deployments don’t try to check for updates


  • Chart.lock is updated during helm dependency update with the gluon library & postgresql dependency


  • Modified to support templating of the data key so that the keycloak chart can be used to create secret for the truststore.jks binary.


  • Quarkus migration: remove http-management port 9990 yaml block. Removed 7 lines near line 50


  • line 1 changed “wildfly” to “metrics”
  • added support for Istio mTLS in the endpoints lines 37-43


  • add extraVolumesBigBang (lines 196-189)
  • add extraVolumeMountsBigBang (lines 146-148)
  • modify pgchecker initContainer (lines 54-64)
  • Quarkus migration: change database environment variable names (lines 89-99)
  • Quarkus migration: remove http-management port 9990 yaml block. Removed 3 lines near line 118


  • add istio virtual service
  • add NetworkPolicies to restrict traffic


  • add /dev directory to hold the the baby-yoda configuration files
  • add the DoD certificate bundle pem file


  • add directory with cypress test files

chart/templates/tests (this is separate from the upstream templates/test directory)📜

  • add helm template to add support for the helm test library


  • update the chart version with the bigbang -bb.#
  • update app version when not the same as the original chart
  • add gluon library dependency
  • Update postgresql dependency for local source
  • add annotations for release automation


  • Upstream bitnami postgresql chart - modified for Iron Bank Postgresql 12.15 runtime.
  • Update security context for user:group 26:26


  • commented out existing -if -else securityContext and replaced with
  • {{- toYaml $.Values.postgesql.containerSecurityContext | nindent 12 }}

Last update: 2024-05-16 by Greg M