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
The Helm chart supports configuring a Horizontal Pod Autoscaler (HPA) to automatically scale the number of pods based on CPU and memory utilization:
414
+
This chart does NOT ship a HorizontalPodAutoscaler. The AI SRE Agent worker is
415
+
a single writer to the pattern catalog and detect log, so the agent must run
416
+
with `replicaCount: 1` — horizontal scaling would produce racing writes (the
417
+
chart fails fast if `agent.enable=true` with more than one replica). For
418
+
deployments that do not enable the agent you may raise `replicaCount`, but the
419
+
number of pods is fixed by that value and is not autoscaled.
410
420
411
421
```yaml
412
-
autoscaling:
413
-
enabled: true
414
-
minReplicas: 2
415
-
maxReplicas: 10
416
-
targetCPUUtilizationPercentage: 80
417
-
targetMemoryUtilizationPercentage: 80
422
+
replicaCount: 1 # required when agent.enable=true
418
423
```
419
424
420
-
For more advanced scaling behavior, you can use the `behavior` configuration:
421
-
422
-
```yaml
423
-
autoscaling:
424
-
enabled: true
425
-
minReplicas: 2
426
-
maxReplicas: 10
427
-
targetCPUUtilizationPercentage: 80
428
-
targetMemoryUtilizationPercentage: 80
429
-
behavior:
430
-
scaleDown:
431
-
stabilizationWindowSeconds: 300
432
-
policies:
433
-
- type: Percent
434
-
value: 100
435
-
periodSeconds: 15
436
-
scaleUp:
437
-
stabilizationWindowSeconds: 0
438
-
policies:
439
-
- type: Percent
440
-
value: 100
441
-
periodSeconds: 15
442
-
- type: Pods
443
-
value: 4
444
-
periodSeconds: 15
445
-
selectPolicy: Max
446
-
```
447
-
448
-
Note: When enabling autoscaling, the `replicaCount` value in your values.yaml is only used for the initial deployment before the HPA takes over scaling control.
449
-
450
425
## Uninstalling the Chart
451
426
452
427
To uninstall/delete the `versus-incident` deployment:
{{- fail (printf"versus-incident: storage.persistence.enabled=true with %d replicas and accessMode=ReadWriteOnce. The PVC cannot be mounted on more than one pod. Set replicaCount=1 (and autoscaling.enabled=false), use accessMode=ReadWriteMany, or switch to a non-file storage backend."$replicas) -}}
53
+
{{- fail (printf"versus-incident: storage.persistence.enabled=true with %d replicas and accessMode=ReadWriteOnce. The PVC cannot be mounted on more than one pod. Set replicaCount=1, use accessMode=ReadWriteMany, or switch to a non-file storage backend."$replicas) -}}
{{- fail (printf"versus-incident: agent.mode=%q is not recognised. Valid values: training, shadow, detect."$mode) -}}
80
77
{{- end -}}
81
78
{{- $replicas:= int (default 1 .Values.replicaCount) -}}
82
-
{{- if.Values.autoscaling.enabled -}}
83
-
{{- $replicas= int (default 1 .Values.autoscaling.minReplicas) -}}
84
-
{{- end -}}
85
79
{{- ifgt$replicas 1 -}}
86
-
{{- fail (printf"versus-incident: agent.enable=true with %d replicas. The agent worker is single-writer to the pattern catalog and detect log; running multiple replicas will produce racing writes. Set replicaCount=1 and autoscaling.enabled=false when running the agent."$replicas) -}}
80
+
{{- fail (printf"versus-incident: agent.enable=true with %d replicas. The agent worker is single-writer to the pattern catalog and detect log; running multiple replicas will produce racing writes. Set replicaCount=1 when running the agent."$replicas) -}}
0 commit comments