Skip to main content

Helm Chart Values Changelog

Track changes in GitGuardian's Helm chart values across releases.

Latest Version: 2026.10.0

Resources: Helm installation guide | Upgrade procedures

2026.10.0 vs 2026.9.0​

New:

Updated:

2026.9.0 vs 2026.8.0​

New:

Updated:

  • The ClickHouse component is now rendered by native chart templates under the single clickhouse.* key, instead of the vendored clickhouse-server subchart. Persistence, resources, scheduling, probes, security contexts, configdFiles, usersdFiles, sidecars and the other subchart settings keep their names but move from clickhouse-server.* to clickhouse.*.
  • clickhouse.serverConfig keys are renamed from environment-variable style to camelCase with typed values: MAX_CONCURRENT_QUERIES becomes maxConcurrentQueries: 32, PARTS_TO_DELAY_INSERT becomes partsToDelayInsert: 1000, and so on. cacheMaxSize now defaults to empty and is derived from clickhouse.cache.size.
  • clickhouse.defaultInitContainers.volumePermissions.image now points at gitguardian/wolfi/bash instead of the os-shell-iamguarded image, which could not be pulled.
  • mcpServer.image.registry now defaults to the Replicated proxy (proxy.replicated.com/proxy/gitguardian/ghcr.io) instead of ghcr.io.
  • Added the team_sync queue to celeryWorkers.long.queues (and the matching team_sync: 10 autoscaling metric).
  • celeryWorkers.automatic-severities.resources.requests now sets cpu: 100m.
  • replicated.supportBundle.resources.initContainer memory defaults rise from 128Mi / 512Mi to 1Gi request / 4Gi limit, so bundle generation no longer runs out of memory on large instances.
  • Added the optional celeryWorkers.container-registries worker (container_registries queue, replicas: 0, fallbackWorker: scanners).

Removed:

2026.8.0 vs 2026.7.0​

New:

Updated:

2026.7.0 vs 2026.6.0​

New:

  • Added the optional celeryWorkers.public-monitoring worker, which consumes the Public Monitoring queues (public_monitoring, public_monitoring_historical_scan, public_monitoring_realtime_scan). It is gated by the is_public_monitoring_enabled license field (effectively disabled until licensed); when enabled it defaults to 1 replica, 1Gi memory request / 2Gi limit.
  • Added the opt-in mcpServer deployment. Set mcpServer.enabled: true to deploy the MCP server (default false). When enabled it runs 1 replica, exposes an ingress under the /mcp-server path of the application host, enables the OAuth proxy, and uses latency-based autoscaling (mcpServer.autoscaling.metrics.targetLatency). With the aws_alb controller it requires AWS Load Balancer Controller 2.14 or later.
  • Added inAppAnalytics.ephemeralStorage (enabled, size, storageClass, annotations, labels; default enabled: false, size: 20Gi) to attach a dedicated ephemeral volume to the in-app analytics pod, moving Spark scratch and spill data off the node's local /tmp disk. Prevents daily analytics job failures caused by node ephemeral-storage limits on large workspaces. See In-app analytics ephemeral storage.
  • Added logCollector.collectMigrationLogs (default true) to also collect logs from the pre-deploy and post-deploy hook Jobs. The collector is injected as a native sidecar, which requires Kubernetes 1.29 or later. Disable it on older clusters.

Updated:

  • Added the validity_check_batch autoscaling metric to celeryWorkers.batch.

2026.6.0 vs 2026.5.0​

New:

  • Added Gateway API support for ingress. New ingress.routingApi (ingress (default) or gateway-api) selects between the Kubernetes Ingress / IngressRoute / VirtualService / HTTPProxy / Route templates and Gateway API HTTPRoute + Gateway. When gateway-api is selected, configure ingress.gatewayApi.gatewayClassName and ingress.gatewayApi.gateway.* (create, name, namespace, httpListenerPort, httpsListenerPort); only the istio, contour, and traefik controllers are supported in this mode. See Gateway API.
  • Added the optional celeryWorkers.check-run-scanners worker — consumes the check_run_scan queue to run scan-based (PR-scoped) check-runs on dedicated pods, separate from the historical-scan scanners worker. Disabled by default (replicas: 0); when disabled, the check_run_scan queue falls back to the scanners worker. Autoscaling metric {"check_run_scan":10}, terminationGracePeriodSeconds: 1800.
  • Added the optional celeryWorkers.premium-scanners-retry worker — consumes the premium_repo_scan_retry queue and retries failed large-repository scans on a dedicated high-memory pod. Disabled by default (replicas: 0); when disabled, retries fall back to the regular scanner workers. Defaults: 120Gi memory request/limit, autoscaling metric {"premium_repo_scan_retry":1}, terminationGracePeriodSeconds: 86400. See Premium scan retry worker.
  • Added the premium_repo_scan_retry queue so retries are processed by the standard celeryWorkers.scanners worker when the dedicated worker is disabled.
  • Added tls.customCa.resources to set resource requests/limits on the init-custom-ca init container (default: requests cpu: 50m / memory: 64Mi, limits memory: 128Mi).

Updated:

  • webapps.internal_api_long.nginx.location now also routes issues/{id}/occurrences/ and public-monitoring/perimeter/all-developers/ to the long-request internal API webapp (previously only the report/ endpoint).

2026.5.0 vs 2026.4.0​

New:

Updated:

Removed:

2026.4.0 (Required) vs 2026.3.0​

New:

Updated:

Removed:

2026.3.0 vs 2026.2.0​

Updated:

2026.2.0 vs 2026.1.0​

New:

Updated:

2026.1.0 (Required) vs 2025.12.0​

New:

  • Added webappDefaults and celeryWorkerDefaults sections to centralize common configuration (e.g., nodeSelector, tolerations, priorityClassName). Individual webapp/worker configurations are still fully supported and take priority over defaults - you can override any default value by specifying it directly under webapps.[name] or celeryWorkers.[name], even if not explicitly listed in the values reference.
  • Added new Celery queues: core_default and core_long.

Removed:

  • Removed apacheTika.javaOpts parameter.

2025.12.0 vs 2025.11.0​

New:

Updated:

2025.11.0 vs 2025.10.0​

New:

Updated:

Removed:

  • Deleted replicatedSdk key as it is enabled by default now.

2025.10.0 (Required) vs 2025.9.0​

Updated:

Removed:

  • loki-minio.podSecurityContext.enabled boolean has been removed. To disable podSecurityContext you now need to use empty object such as podSecurityContext: {}.
  • loki-minio.containerSecurityContext.enabled boolean has been removed. To disable containerSecurityContext you now need to use empty object such as containerSecurityContext: {}.
  • loki-minio.networkPolicy section has been removed since it is not supported anymore.
  • loki-minio.console section has been removed since it is not relevant anymore.
  • loki-minio.ServiceAccount section has been removed since it is now enabled by default.

2025.9.0 vs 2025.8.0​

New:

  • Introduced apacheTika parameter to configure the new file scanner service for Non-VCS sources (disabled by default).
  • Introduced celeryWorkers.scanners-ods-highdisk parameter to configure workers dedicated to high storage tasks like Microsoft OneDrive and SharePoint scanning (default: 0).

Learn more about Non-VCS Sources.

Updated:

Removed:

2025.8.0 vs 2025.7.0​

Upgrading to 2025.8

Air gap deployment? This release introduces a new image.registry parameter in Helm values to support the Log Collector system. This parameter specifies the location of the GitGuardian images for the Log Collector components (Loki, MinIO, Fluent Bit) and is separate from the main imageRegistry parameter. Follow the upgrade instructions to update your helm values file.

New:

  • Introduced a new image.registry parameter in Helm values to support the Log Collector system. This parameter specifies the location of the GitGuardian images for the Log Collector components (Loki, MinIO, Fluent Bit) and is separate from the main imageRegistry parameter. Follow the upgrade instructions to update your helm values file.
  • Introduced celeryWorkers.scanners-slack parameter to configure workers dedicated to Slack scanning (default: 0). Learn more about Slack Scanning considerations.
  • Added commonTolerations parameter that allows you to apply consistent tolerations across all workloads in the GitGuardian deployment.

Removed:

  • beat.replicas has been removed and is now hardcoded in the chart to 1.

2025.7.0 (Required) vs 2025.6.0​

New:

  • Added priorityClassName parameter for ML Secret Engine and several priority class configuration. Learn more. This is also available for other pods and as a global parameter (global.priorityClassName).

Updated:

2025.6.0 vs 2025.5.0​

New:

Removed:

  • migration.resources has been replaced with job-specific resource configurations for better resource management.

2025.5.0 vs 2025.4.0​

Upgrading to 2025.5

Air gap deployment? We've renamed images in this release. See below changes and find all image and tag names on the Air Gap Install page.

New:

Updated:

  • FIPS: This release uses Chainguard images without FIPS-approved cryptographic modules. If you would like to use Chainguard images with FIPS, please contact our support team. This change involves renaming the following images:
    • gitguardian/prm-static-chainguard-fips to gitguardian/prm-static-chainguard
    • gitguardian/prm-app-fips to gitguardian/prm-app-chainguard
  • Use proxy.replicated.com/proxy/gitguardian/ghcr.io/gitguardian/wolfi/bash:latest image instead of proxy.replicated.com/proxy/gitguardian/docker.io/nginxinc/nginx-unprivileged:stable for Custom CA injection (See tls.customCa.image.*).
  • The securityContext.enabled (bool) parameter has been replaced by a new securityContext (object) parameter, which now allows specifying the full Pod Security Context.

Removed:

  • experimental.chainguard has been deprecated as GitGuardian images are now using Chainguard by default. Lean more about Chainguard.

2025.4.0 (Required) vs 2025.3.0​

Upgrading to 2025.4

Air gap deployment? We've added new images in this release. Find all image and tag names on the Air Gap Install page.

New:

  • Our self-hosted deployments now include a log collection system, leveraging Loki, MinIO, and Fluent Bit under the hood. This log collection system is now enabled by default for all installation types (Helm or KOTS). Learn more about the log collector.
  • The PostgreSQL pgvector extension is now required by default (postgresql.plugins.pgvector.enabled). Please follow the installation instructions to enable vector similarity search capabilities for upcoming machine learning features.

Updated:

2025.3.0 vs 2025.2.0​

Upgrading to 2025.3

We've updated the path and names of our images in this release. Follow the upgrade instructions to update your tooling for downloading and uploading GitGuardian images to your private registry. Find all image and tag names on the Air Gap Install page.

Updated:

  • Change registry URL from proxy.replicated.com/proxy/gitguardian/513715405986.dkr.ecr.us-west-2.amazonaws.com to proxy.replicated.com/proxy/gitguardian/docker.io and rename paths and images name from:
    • /prm/static-chainguard to /gitguardian/prm-static-chainguard-fips
    • /prm/app-chainguard to /gitguardian/prm-app-chainguard-fips
    • /prm/helm-tooling to /gitguardian/prm-helm-tooling
    • /services/nginx-unprivileged to /nginxinc/nginx-unprivileged
    • /ml-detector/ml-secret-engine/app-chainguard to /gitguardian/ml-secret-engine-app-chainguard-fips
  • Change registry URL from registry.replicated.com to proxy.replicated.com/proxy/gitguardian/docker.io and rename paths and images name from /gitguardian/replicated-sdk to /replicated/replicated-sdk.
  • The nhi-scout parameter has been renamed to ggscout.
  • Added celeryWorkers.*.autoscaling.keda.idleReplicaCount parameter to allow specifying the number of replicas when there is no activity on the Celery Worker (default: 0).

2025.2.0 vs 2025.1.0​

New:

Updated:

  • nhiScout.enabled parameter has been moved to nhi-scout.enabled. Learn more.

2025.1.0 (Required) vs 2024.12.0​

Upgrading to 2024.12

The ReplicatedSDK image is now pulled from the Replicated registry instead of Docker Hub. For airgap installations, ensure you update your automation processes for pulling and pushing images to your private registry. For more information, refer to the Airgap Installation page.

New:

  • Introduced secretEngine parameter to configure the new ML Secret Engine service. (Disabled by default). Learn more.
  • Introduced celeryWorkers.ml-api-priority parameter to configure ML Secret Engine dedicated worker (Disabled by default).
  • Introduced nhiScout.enabled parameter to enable NHI Scout deployment (Disabled by default). Learn more
  • Introduced nhi-scout parameter to configure NHI Scout.
  • Added replicated.image.registry parameter to use the Replicated registry (registry.replicated.com) instead of Docker Hub by default.

Updated:

2024.12.0 vs 2024.11.0​

Upgrading to 2024.12

This release includes breaking changes. Upgrade to 2024.12.0 using the upgrade notes.

New:

  • Ability to deploy Ingress objects with the support of several Ingress controllers. For details, see the Ingress documentation.

Updated:

  • front.ingress has been renamed to ingress for improved consistency and standardization across the Helm chart.
  • istio have been moved under the ingress.
  • The default memory value for migration.resources has been increased from 100Mi to 200Mi.

2024.11.0 vs 2024.10.0​

Upgrading to 2024.11

This release includes breaking changes.

New:

  • Removed settings.healthCheck.periodicInterval parameter since health checks are now distributed over time rather than executing them simultaneously. This parameter is replaced by spread_periodic_range_minutes in the admin area.
  • Added replicated.privateCASecret parameter to specify a custom CA when using a proxy. Learn more.
  • Replace the legacy parameter replicated.images.replicated-sdk with the new parameters replicated.image.repository and replicated.image.tag

2024.10.0 (Required) vs 2024.9.0​

New:

  • Added two new worker types long-ods (non-VCS sources such as Slack, Jira Cloud, Confluence, ...) and long-ods-io (long tasks specialized in Input/Output).
  • Added the support of CRL (instead of default OCSP) for certificate-based authentication.

Updated:

2024.9.0 vs 2024.8.0​

New:

2024.8.0 vs 2024.7.0​

New:

  • Introduced tls.clientAuth to support authentication using Common Access Card (CAC) or Personal Identity Verification (PIV). For detailed information, refer to the documentation here.

2024.7.0 (Required) vs 2024.6.0​

Upgrading to 2024.7

This release includes breaking changes.

New:

  • Added settings.healthCheck.periodicInterval allowing you to change the frequency of health checks.

Updated:

2024.6.0 vs 2024.5.0​

Updated:

2024.5.0 vs 2024.4.0​

Upgrading to 2024.5

This release includes breaking changes.

New:

Updated:

  • Replaced postgresql.existingSecretKeys.tls with postgresql.tls.existingSecretKeys and set the Default to "" for
    • password instead of POSTGRES_PASSWORD.
    • crt instead of ``"pg_client.crt"`.
    • key instead of "pg_client.key".
    • caCrt instead of "pg_server.ca_crt".
  • Replaced redis.main.existingSecretKeys.tls with redis.main.tls.existingSecretKeys and set the Default values to "" for
    • crt instead of ``"redis_client.crt"`.
    • key instead of "redis_client.key".
    • caCrt instead of "redis_server.ca_crt".
  • Replaced redis.commitCache.existingSecretKeys.tls with redis.commitCache.tls.existingSecretKeys and set the Default values to "" for
    • crt instead of ``"redis_client.crt"`.
    • key instead of "redis_client.key".
    • caCrt instead of "redis_server.ca_crt".
  • Rename celeryWorkers.realtime_ods to celeryWorkers.realtime-ods.
  • Set the Default for miscEncryption.existingSecretKeys attributes to "" for
    • djangoSecretKey instead of "DJANGO_SECRET_KEY".
    • dbEncryptionKeys instead of "ENCRYPTION_KEYS".
    • x509Cert instead of "SP_X509_CERT".
    • x509PrivateKey instead of "SP_PRIVATE_KEY".
  • Added "existingSecret":"","existingSecretKeys":{"password":""} in onPrem.adminUser offering the option to specify the admin password in a secret.
  • Rename Default value for tls.customCa.existingSecretCaCertKey to "ca.crt" instead of "custom-ca.pem".
  • Added report to celeryWorkers.worker.queues.

Removed:

  • Removed argoCd.enabled originally used to inject Argo CD phase annotations in Kubernetes resources but, since Argo CD supports Helm hooks annotations by mapping them onto its own hook annotations, it is not used anymore in 2024.5.0.

2024.4.0 (Required) vs 2024.3.0​

New:

Updated:

2024.3.0 vs 2024.2.0​

Updated:

  • Decreased the default value of celeryWorkers.scanners_ods.replicas from 2 to 0.

2024.2.0 vs 2024.1.0​

New:

Removed:

  • Removed observability.exporters.celeryExporter.

2024.1.0 (Required) vs 2023.12.0​

New:

Updated:

  • Added new tasks realtime_ods,realtime_retry_ods to celeryWorkers.worker.queues to support additional task types.
  • Enabled experimental.chainguard by default, changing from false to true, to utilize Chainguard images for backend and frontend services.