You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(helm): support pre-provisioned PVC for telemetry Redis
Adds telemetry.redis.persistence.existingClaim so operators on clusters
without a dynamic PV provisioner (or wanting to reuse a volume across
releases) can hand the chart a pre-created PVC instead of relying on
chart-managed provisioning. When set, the chart skips its PVC render and
the Deployment mounts the named claim; persistence.enabled=false still
wins and yields an emptyDir.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: helm/fiftyone-teams-app/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1092,6 +1092,7 @@ If pods show unhealthy states (e.g., `0/1`, `CrashLoopBackOff`, `Pending`):
1092
1092
| telemetry.redis.maxmemory | string | `"400mb"` | `--maxmemory` flag passed to `redis-server`. |
1093
1093
| telemetry.redis.maxmemoryPolicy | string | `"allkeys-lru"` | `--maxmemory-policy` flag passed to `redis-server`. |
1094
1094
| telemetry.redis.persistence.enabled | bool | `true` | Controls whether a `PersistentVolumeClaim` is created for the bundled telemetry Redis. When `false`, Redis runs with an `emptyDir` volume and state is lost on pod restart — fine for dev clusters without a dynamic PV provisioner, not for production. |
1095
+
| telemetry.redis.persistence.existingClaim | string | `""` | Name of an existing `PersistentVolumeClaim` (in `namespace.name`) to bind the telemetry Redis to. When set, the chart will NOT create a `PersistentVolumeClaim` and the `size` / `storageClass` fields above are ignored — you are responsible for provisioning the claim out of band. Use this on clusters without a dynamic PV provisioner, or to reuse an existing volume across releases. Has no effect when `persistence.enabled` is `false`. |
1095
1096
| telemetry.redis.persistence.size | string | `"1Gi"` | Storage size for the telemetry Redis `PersistentVolumeClaim`. |
1096
1097
| telemetry.redis.persistence.storageClass | string | `""` | `StorageClass` name for the telemetry Redis `PersistentVolumeClaim`. Leave unset to use the cluster's default `StorageClass`. |
1097
1098
| telemetry.redis.podSecurityContext | object | `{"fsGroup":999,"runAsGroup":999,"runAsNonRoot":true,"runAsUser":999}` | Pod-level security attributes for the telemetry Redis. Defaults to a non-root UID/GID matching the `redis` user in the upstream `redis:7-alpine` image (999). `fsGroup` ensures the mounted `/data` volume is group-writable. [Reference][security-context]. |
Copy file name to clipboardExpand all lines: helm/fiftyone-teams-app/values.schema.json
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -4017,6 +4017,12 @@
4017
4017
"title": "enabled",
4018
4018
"type": "boolean"
4019
4019
},
4020
+
"existingClaim": {
4021
+
"default": "",
4022
+
"description": "Name of an existing `PersistentVolumeClaim` (in `namespace.name`) to\nbind the telemetry Redis to. When set, the chart will NOT create a\n`PersistentVolumeClaim` and the `size` / `storageClass` fields above\nare ignored — you are responsible for provisioning the claim out of\nband. Use this on clusters without a dynamic PV provisioner, or to\nreuse an existing volume across releases. Has no effect when\n`persistence.enabled` is `false`.",
4023
+
"title": "existingClaim",
4024
+
"type": "string"
4025
+
},
4020
4026
"size": {
4021
4027
"default": "1Gi",
4022
4028
"description": "Storage size for the telemetry Redis `PersistentVolumeClaim`.",
0 commit comments