Updated
- Bumping chart version to v0.5.74 for scalr-agent v1.0.1
Added
-
Made the data directory persistence configurable. The
persistence.datablock now supports the sameenabled/emptyDir/persistentVolumeClaimstructure aspersistence.cache, allowing the data volume to be backed by a PVC instead ofemptyDir. Example:persistence: data: enabled: true persistentVolumeClaim: storageClassName: "" # use cluster default storage: 4Gi accessMode: ReadWriteOnce cache: enabled: true persistentVolumeClaim: storageClassName: "nfs-client" storage: 40Gi accessMode: ReadWriteMany # share cache across replicas
-
Persistence schema is now symmetric between
persistence.dataandpersistence.cache, matching theagent-jobchart.
Deprecated
-
The top-level
persistence.enabledandpersistence.persistentVolumeClaim.*keys are deprecated in favor ofpersistence.cache.enabledandpersistence.cache.persistentVolumeClaim.*. The legacy keys still work and the chart emits a deprecation warning viaNOTES.txtwhen they are used. They will be removed in a future release.Backward compatibility: existing installations continue to work without any values changes. When the legacy keys are set, the chart maps them onto the cache volume and preserves the legacy default cache PVC name (
<release-fullname>) to avoid orphaning existing PVCs on upgrade. On the new schema, the default cache PVC name is<release-fullname>-cacheand the new data PVC default name is<release-fullname>-data.Action required (recommended migration): move legacy values under
persistence.cache.*. Before:persistence: enabled: true persistentVolumeClaim: claimName: "my-cache-pvc" storageClassName: "nfs-client" storage: 40Gi accessMode: ReadWriteMany
After:
persistence: cache: enabled: true persistentVolumeClaim: claimName: "my-cache-pvc" storageClassName: "nfs-client" storage: 40Gi accessMode: ReadWriteMany
When you migrate without specifying
claimNameand previously relied on the auto-created PVC, note that the default PVC name changes from<release-fullname>to<release-fullname>-cache. To keep using the existing PVC, setpersistence.cache.persistentVolumeClaim.claimName: "<release-fullname>"explicitly, or rename/re-bind the underlying PV.