Release [jfrog-platform] 11.6.2 · jfrog/charts

Platform Chart Details

	Previous	New	Status
Chart Version	`11.6.1`	`11.6.2`	🔄 Updated
App Version	`7.161.16`	`7.161.19`	🔄 Updated

Changelog (`11.6.1` → `11.6.2`)

Update dependency artifactory chart version to 107.161.19
Update dependency xray chart version to 103.150.33
Update dependency catalog chart version to 101.44.0

Dependency Chart Version Summary

Dependency	Previous	New	Status
postgresql	`16.7.26`	`16.7.26`	Unchanged
rabbitmq	`15.4.1`	`15.4.1`	Unchanged
artifactory	`107.161.16`	`107.161.19`	🔄 Updated
xray	`103.150.23`	`103.150.33`	🔄 Updated
catalog	`101.43.5`	`101.44.0`	🔄 Updated
distribution	`102.52.16`	`102.52.16`	Unchanged
worker	`101.216.0`	`101.216.0`	Unchanged
bridge	`101.262.34`	`101.262.34`	Unchanged
wingman	`100.606.22`	`100.606.22`	Unchanged

Dependency Changes

Artifactory (`107.161.16` → `107.161.19`) _{📖 Official release notes: artifactory 7.161.19}

Changelog

[107.161.19] - Aug 04, 2026

Added nginx.customConfFile and nginx.customServerSnippet to extend the nginx configuration without replacing it GH-2290

Xray (`103.150.23` → `103.150.33`) _{📖 Official release notes: xray 3.150.33}

Changelog

[103.150.33] - Jun 26, 2026

Valkey maxmemory and maxmemory-policy are now set by the sizing profiles
Valkey shipped without a maxmemory, which leaves the dataset unbounded: rather than evicting, a Valkey node grows until it reaches its container memory limit and is OOMKilled by the kernel. With Sentinel that costs a failover, and the replacement node fills up the same way.
Breaking change: Valkey Sentinel enabled by default — the Valkey StatefulSet and its PVCs are replaced
What changed: Valkey now runs in replication + Sentinel (HA) mode — valkey.architecture: replication, valkey.replica.replicaCount: 3, valkey.sentinel.enabled: true. Chart versions up to and including 103.143.0 ran valkey.architecture: standalone with valkey.replica.replicaCount: 0.
Who is affected: only environments that already have valkey.enabled: true deployed. Valkey is disabled by default.
Standalone mode deploys a single StatefulSet <release>-valkey-primary; with Sentinel the chart deploys <release>-valkey-node with all nodes in one StatefulSet. Because the name differs, helm upgrade creates the new StatefulSet and removes the old one instead of updating it — so the upgrade itself does not fail, but the PVCs are recreated rather than migrated. A StatefulSet's volumeClaimTemplates is immutable, so the claims cannot be carried across the replacement: the new StatefulSet provisions its own valkey-data-<release>-valkey-node-<ordinal> PVCs, one per node, and valkey-data-<release>-valkey-primary-0 is neither reused nor deleted.
Two consequences:
- The cached data is discarded. Valkey here only backs the catalog cache, so it repopulates on demand and no action is required.
- The old PVC is left behind. StatefulSet PVCs carry no ownerReferences, so deleting the StatefulSet does not delete them and nothing reclaims them automatically — the volume stays allocated until removed by hand. After the upgrade:
```
kubectl get pvc -l app.kubernetes.io/name=valkey,app.kubernetes.io/instance=<release> --namespace <namespace> -o name | grep -E '/valkey-data-.*-valkey-(primary|replicas)-'
kubectl get pvc -l app.kubernetes.io/name=valkey,app.kubernetes.io/instance=<release> --namespace <namespace> -o name | grep -E '/valkey-data-.*-valkey-(primary|replicas)-' \
  | xargs -r kubectl delete --namespace <namespace>
```
Also note that storage goes from one Valkey PVC to one per node (three by default), so confirm the StorageClass can provision that before upgrading.

Breaking change: Valkey PVC size default increased from 1Gi to 200Gi
What changed: valkey.primary.persistence.size and valkey.replica.persistence.size both moved from 1Gi to 200Gi. With Sentinel enabled — the default since 103.150.33 — all Valkey nodes run in one StatefulSet whose PVC size comes from valkey.replica.persistence.size; valkey.primary.persistence.size has no effect in that mode.
Who is affected: only environments that already have valkey.enabled: true deployed. Fresh installs with valkey.enabled: true create Valkey PVCs at 200Gi and need no extra steps; default chart installs leave Valkey disabled and create no Valkey PVCs.
Why an upgrade needs a manual step: a PVC size lives in the StatefulSet's volumeClaimTemplates, and Kubernetes treats that field as immutable once the StatefulSet exists, so the StatefulSet has to be replaced for the new size to take effect. Where the StatefulSet keeps its name, helm upgrade would otherwise fail with:

Forbidden: updates to statefulset spec for fields other than 'replicas', 'ordinals', 'template', 'updateStrategy', 'persistentVolumeClaimRetentionPolicy' and 'minReadySeconds' are forbidden

On an upgrade of an existing valkey.enabled: true release, the chart stops with the steps below printed instead.
Step 1 — See which Valkey objects the release has. The object names depend on the architecture the release was deployed with, so discover them rather than assuming a layout or a replica count. Filtering on the valkey-data- prefix keeps Sentinel's sentinel-data PVCs out of the resize — they carry identical labels, hold Sentinel state rather than cache, and must be left alone.

kubectl get statefulset -l app.kubernetes.io/name=valkey,app.kubernetes.io/instance=<release> --namespace <namespace> -o name
kubectl get pvc -l app.kubernetes.io/name=valkey,app.kubernetes.io/instance=<release> --namespace <namespace> -o name | grep '/valkey-data-'

Each command in the following steps re-runs that lookup and pipes it into kubectl. Do not collect the list into a shell variable and pass it unquoted — zsh does not split it into separate arguments, and kubectl rejects it with arguments in resource/name form may not have more than one slash.
Both must return something before continuing. The StatefulSet name tells you which case you are in:

StatefulSet	Deployed from	PVCs	Use
`<release>-valkey-primary` (and `-valkey-replicas`)	103.143.x or earlier — `architecture: standalone`, `replicaCount: 0`	`valkey-data-<release>-valkey-primary-0`	Step 3b
`<release>-valkey-node`	103.150.x or later — replication + Sentinel	`valkey-data-<release>-valkey-node-0` … `-<replicaCount - 1>`	Step 3a or 3b
In the first case this upgrade also moves the release to the Sentinel layout, whose StatefulSet is named `<release>-valkey-node`. Because that is a different name, Helm creates it and removes the old StatefulSet, and it provisions its own PVCs at 200Gi — the old `valkey-data` PVCs are not reused, and StatefulSet PVCs carry no `ownerReferences`, so nothing reclaims them automatically. Step 3b deletes them.
Step 2 — Check whether volume expansion is enabled in the StorageClass of the Valkey PVCs

kubectl get pvc -l app.kubernetes.io/name=valkey,app.kubernetes.io/instance=<release> --namespace <namespace> -o name | grep '/valkey-data-' \
  | xargs -r kubectl get --namespace <namespace> -o custom-columns=NAME:.metadata.name,SIZE:.spec.resources.requests.storage,CLASS:.spec.storageClassName
kubectl get storageclass <storage-class> -o jsonpath='{.allowVolumeExpansion}'

If the SIZE column already reads 200Gi, there is nothing to resize — skip to step 4.
Step 3 — Replace or expand the PVCs
3a. Expand in place — keeps the cached data. Only for a <release>-valkey-node StatefulSet and allowVolumeExpansion: true. Patching PVCs that belong to a -valkey-primary / -valkey-replicas StatefulSet has no effect on this upgrade: the new Sentinel StatefulSet creates its own PVCs, and the patched ones are left behind — stuck part-expanded if the StorageClass has no resizer.

kubectl delete statefulset -l app.kubernetes.io/name=valkey,app.kubernetes.io/instance=<release> --namespace <namespace>
kubectl get pvc -l app.kubernetes.io/name=valkey,app.kubernetes.io/instance=<release> --namespace <namespace> -o name | grep '/valkey-data-' \
  | xargs -r -I{} kubectl patch {} --namespace <namespace> --type=json -p '[{"op": "replace", "path": "/spec/resources/requests/storage", "value": "200Gi"}]'

3b. Replace — discards the cache, and works for either layout on any StorageClass. Valkey here only backs the catalog cache, so its data is disposable and repopulates on demand. Delete the StatefulSet before the PVCs: while its pods are running, PVC deletion blocks on the in-use protection finalizer.

kubectl delete statefulset -l app.kubernetes.io/name=valkey,app.kubernetes.io/instance=<release> --namespace <namespace>
kubectl get pvc -l app.kubernetes.io/name=valkey,app.kubernetes.io/instance=<release> --namespace <namespace> -o name | grep '/valkey-data-' \
  | xargs -r kubectl delete --namespace <namespace>

Step 4 — REQUIRED: add this to your custom values file. The upgrade stays blocked until it is present, and it must stay there for all future upgrades.

valkeyPvcResizeAcknowledged: true

Step 5 — Run the upgrade again

helm upgrade <release> ... --namespace <namespace>

Already on 200Gi, or already done steps 1-3? Then only steps 4 and 5 are needed.

Catalog (`101.43.5` → `101.44.0`)

Changelog

No changelog entries in range 101.44.0 .. 101.43.5.

Image Version Summary

Artifactory (`107.161.16` → `107.161.19`)

Images

Image (repository)	Previous Tag	Current Tag	Status	Digest
InitContainers (`jfrog/echo-mini`)	`20260716`	`20260716`	Unchanged	`sha256:1d41ca84e71f3be4deff268ba723cc1187f0e64d141328ecbaf25254f5aec1d6`
Router (`jfrog/router`)	`7.729.23`	`7.729.42`	🔄 Updated	`sha256:94b42ba8701dfcc65824860f14aec78f4a153697e56ffa25eb425963c3adba07`
Artifactory (`jfrog/artifactory-pro`)	`7.161.16`	`7.161.19`	🔄 Updated	`sha256:c6ae084ea39530a28d5a51ebdcb30eab63b976f4b58a0ce69ca822f7b75e6625`
Frontend (`jfrog/frontend`)	`1.652.21`	`1.652.41`	🔄 Updated	`sha256:5447a4efd89d2be30e931bde6250fdfafca33caa4338a3f26c47d4db7fc423ec`
Observability (`jfrog/observability`)	`2.47.5`	`2.47.9`	🔄 Updated	`sha256:1fd037f5ffdddae9aa0fbfc5fb795a28a11ed52b73e215f31358c539505d6e62`
Nginx (`jfrog/nginx-artifactory-pro`)	`7.161.16`	`7.161.19`	🔄 Updated	`sha256:3ae2d9c099a21c5e6d30d49cd3a015abdd7430f1609b41a60342072be6c2cae3`
Postgresql (`echohq/postgres`)	`17.10-helm-20260716`	`17.10-helm-20260716`	Unchanged	`sha256:3d89ab4d17fbc09d532db88a05b4d83cc21fde0b6a7f8b4717ee3c118915e7c4`
Filebeat (`beats/filebeat`)	`7.16.2`	`7.16.2`	Unchanged	unavailable
Rtfs (`jfrog/artifactory-federation`)	`2.126.10`	`2.126.22`	🔄 Updated	`sha256:fc6376e881f947b96444dbd6e706ac74b125107fa1150eeb78f76c5187fd32ac`
Apptrust (`jfrog/apptrust`)	`1.86.5`	`1.86.8`	🔄 Updated	`sha256:1a7dbfb9b88e954e12793f1c676af26ac926719cba644e44fbb695a697ace2b7`
Jfbus (`jfrog/jfbus-service`)	`1.386.2`	`1.386.17`	🔄 Updated	`sha256:de91b145be1ad246b5904e89096e58a720f6a2c43a823175dc167cb697e5ca4a`
Jfmelt (`jfrog/jfmelt`)	`1.12.4`	`1.12.6`	🔄 Updated	`sha256:172ce414f1454b4ac36f34ffde6f6eccc572bd3857196abb6cf80c4481b5bbaf`
Unifiedpolicy (`jfrog/unifiedpolicy`)	`1.70.7`	`1.70.11`	🔄 Updated	`sha256:cc46989bdcbceded3e269b452268d164fffe8beb8536413f50f10956b01a2bf4`
Evaluation (`jfrog/evaluation`)	`1.27.9`	`1.27.14`	🔄 Updated	`sha256:f035dfc501d6c60a5735ef28362218879844557ee70d451632244ba892f5ba05`
Platformfederation (`jfrog/platformfederation`)	`1.1328.9`	`1.1328.12`	🔄 Updated	`sha256:9b84e88d03633de02dd7b77e9fcc93a6515288fb117d28ac3eae443230dfbe46`

Xray (`103.150.23` → `103.150.33`)

Images

Image (repository)	Previous Tag	Current Tag	Status	Digest
InitContainers (`jfrog/echo-mini`)	`20260805`	`20260819`	🔄 Updated	`sha256:69d929cb3b4f6c68f4c4934ed42514d6d61983e68594afb0312d59e86a0c1f50`
Postgresql (`echohq/postgres`)	`17.10-helm`	`17.10-helm`	Unchanged	`sha256:3f6423127b2cfa4cd7fa24e997ffce2ef4a079b6989ed3ca92a521b82878cd50`
Rabbitmq (`bitnami/rabbitmq`)	`3.13.7-debian-12-r6`	`3.13.7-debian-12-r6`	Unchanged	`sha256:fc552f869ddedbba09e78a546f876c8712bed53ce887f9e78acd7dba705bba0e`
Rabbitmq.migration (`echohq/kubectl`)	`1.35.6`	`1.35.6`	Unchanged	`sha256:59b0cb0b7384bdd45837a7264f4980c2403c1af6577e38b437377a2eb66e4bdd`
Valkey (`bitnami/valkey`)	`8.1.6-echo`	`8.1.6-echo`	Unchanged	`sha256:edf97f1a567850432a41f420a429b85465e62ec629565f436023e9b7d4a1fc0d`
Valkey.sentinel (`bitnami/valkey-sentinel`)	`8.1-echo`	`8.1-echo`	Unchanged	`sha256:f15039056c9337629c750cfe943e00accd98276f213b4242890837a21e032b8c`
Valkey.kubectl (`echohq/kubectl`)	`1.35.6`	`1.35.6`	Unchanged	`sha256:59b0cb0b7384bdd45837a7264f4980c2403c1af6577e38b437377a2eb66e4bdd`
Analysis (`jfrog/xray-analysis`)	`3.150.23`	`3.150.33`	🔄 Updated	`sha256:5474df9e6b336237a8c03ae56d7511228fedc8c8e6d20583b5ca7f13a38b792b`
Sbom (`jfrog/xray-sbom`)	`3.150.23`	`3.150.33`	🔄 Updated	`sha256:abf4c0824cf2acf1d125784aec478844c091d856d6aef9924a2f6b95f9f73749`
Jascontextual (`jfrog/xray-jascontextual`)	`3.150.23`	`3.150.33`	🔄 Updated	`sha256:7f89a5e88f4dfbd65c4611002e63a33e8b663492a4a064d693ebb3d54ea49da2`
Jasexposures (`jfrog/xray-jasexposures`)	`3.150.23`	`3.150.33`	🔄 Updated	`sha256:e7a32c476371b41a3cd3e0e3bdef4ca4e3dc2ed3d5596fbf948492b02ab81238`
Aiscanner (`jfrog/xray-aiscanner`)	`3.150.23`	`3.150.33`	🔄 Updated	`sha256:b9be96c66c868e08c7e71375527b0a87354d58211bf857367a1b81afd5c6b8fa`
Policyenforcer (`jfrog/xray-policyenforcer`)	`3.150.23`	`3.150.33`	🔄 Updated	`sha256:0292f824db305482a12efd17bfdcbfdb982578abc6bd8637b27ae6e671b25c63`
Indexer (`jfrog/xray-indexer`)	`3.150.23`	`3.150.33`	🔄 Updated	`sha256:183d3f4eec8d54ecab37ec7f1a5f080e9b1bff82af65bf085e27a6c2c8a4ae67`
Persist (`jfrog/xray-persist`)	`3.150.23`	`3.150.33`	🔄 Updated	`sha256:2250bc56ad4e0bca15e261cd298b1b204e4bed4f1c54d7b0bd010973f2622357`
Curation (`jfrog/xray-curation`)	`3.150.23`	`3.150.33`	🔄 Updated	`sha256:c8f32d30b1cb9d043bdcf2e6443de5ee40a4ef3d25a456df7ce999e232bd55ab`
Reporting (`jfrog/xray-reporting`)	`3.150.23`	`3.150.33`	🔄 Updated	`sha256:05212958306e7f9c48d21aa5fe0451500ddb4819b248938f643e32193ea84de1`
Server (`jfrog/xray-server`)	`3.150.23`	`3.150.33`	🔄 Updated	`sha256:c3bd1384ffec250bf42dda8ebf82a02e8a6f935d01e7ed100212e678f3635552`
ContextualAnalysis (`jfrog/xray-jas-contextual-analysis`)	`3.150.23`	`3.150.33`	🔄 Updated	`sha256:7c3b11fb5f2935998f86fc19b4da33fc0bef61955cde90aecb7f38b41807163c`
Exposures (`jfrog/xray-jas-exposures`)	`3.150.23`	`3.150.33`	🔄 Updated	`sha256:b76eba3e0e207bc66fb9fa5eabce024ddacbe69043ff37f55a79fe99772a12db`
Router (`jfrog/router`)	`7.729.34`	`7.729.47`	🔄 Updated	`sha256:49d4981c8e8ae55262d89494f4c5f8707be93d55b21d2515a7e9865e156edb10`
Observability (`jfrog/observability`)	`2.54.0`	`2.58.0`	🔄 Updated	`sha256:8a03df182593262a5111d495fc75ae84831fbe69b99e3b018ffeb741c2379f09`
Filebeat (`beats/filebeat`)	`7.16.2`	`7.16.2`	Unchanged	unavailable

Catalog (`101.43.5` → `101.44.0`)

Images

Image (repository)	Previous Tag	Current Tag	Status	Digest
Catalog (`jfrog/catalog`)	`1.43.5`	`1.44.0`	🔄 Updated	`sha256:9db66ed25bdd86e49888b32cd12c977c5237ebf9eb07bd5275d1a2045ff04f4e`
Router (`jfrog/router`)	`7.729.23`	`7.729.23`	Unchanged	`sha256:3f6ca400bc31b357a0942a6b3d1c56312a3c43e95d12eed1b01bb10416861b2a`
InitContainers (`jfrog/echo-mini`)	`20260730`	`20260730`	Unchanged	`sha256:4938a0f2c0b99566aab5d45e63368156c0adafbbbf0c825cdc3cb0358a5a7ec7`

Navigation Menu

Repository navigation

[jfrog-platform] 11.6.2

Choose a tag to compare

Sorry, something went wrong.

Sorry, something went wrong.

Uh oh!

No results found

Platform Chart Details

Changelog (`11.6.1` → `11.6.2`)

Dependency Chart Version Summary

Dependency Changes

Artifactory (`107.161.16` → `107.161.19`) _{📖 Official release notes: artifactory 7.161.19}

Xray (`103.150.23` → `103.150.33`) _{📖 Official release notes: xray 3.150.33}

Catalog (`101.43.5` → `101.44.0`)

Image Version Summary

Artifactory (`107.161.16` → `107.161.19`)

Xray (`103.150.23` → `103.150.33`)

Catalog (`101.43.5` → `101.44.0`)

Uh oh!

[jfrog-platform] 11.6.2

Platform Chart Details

Changelog (11.6.1 → 11.6.2)

Dependency Chart Version Summary

Dependency Changes

Artifactory (107.161.16 → 107.161.19) 📖 Official release notes: artifactory 7.161.19

Xray (103.150.23 → 103.150.33) 📖 Official release notes: xray 3.150.33

Catalog (101.43.5 → 101.44.0)

Image Version Summary

Artifactory (107.161.16 → 107.161.19)

Xray (103.150.23 → 103.150.33)

Catalog (101.43.5 → 101.44.0)

Uh oh!

Changelog (`11.6.1` → `11.6.2`)

Artifactory (`107.161.16` → `107.161.19`) _{📖 Official release notes: artifactory 7.161.19}

Xray (`103.150.23` → `103.150.33`) _{📖 Official release notes: xray 3.150.33}

Catalog (`101.43.5` → `101.44.0`)

Artifactory (`107.161.16` → `107.161.19`)

Xray (`103.150.23` → `103.150.33`)

Catalog (`101.43.5` → `101.44.0`)