Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions charts/sombra/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,3 +114,9 @@
* Made OPA `livenessProbe` and `readinessProbe` omitable via `null`, matching the existing `startupProbe` pattern. Setting `opa.readinessProbe: null` no longer renders invalid `readinessProbe: null` YAML.
* **ECS vs EKS failure-mode parity**: On ECS MTS, OPA runs with `essential=false`, so an OPA crash leaves Sombra in service and Seneca fails closed in-app. On EKS, any container readiness probe gates pod Ready; omit OPA readiness (`opa.readinessProbe: null`) so OPA outages do not drain Sombra from Service/ALB endpoints. Keep OPA liveness (default) to restart a wedged sidecar.
* **Non-breaking change**: default OPA probes are unchanged; existing installs keep current behavior unless consumers explicitly set probes to `null`.

## 0.14.0

* Raised default `opa.resources` so the OPA sidecar matches the ECS `opa-mts` Fargate reservation and can burst.
* Requests `50m/64Mi` → `250m/512Mi` (matches ECS `opa-mts` `cpu=256`/`memory=512`); limits `100m/128Mi` → `500m/1Gi` (2x headroom). The previous defaults made `requests` exceed `limits` once consumers bumped requests to `250m/512Mi`, which Kubernetes rejects.
* **Behavior change for opt-in OPA consumers**: deployments with `opa.enabled: true` and no `opa.resources` override now reserve more CPU/memory. Self-hosted consumers that pinned the old defaults should set `opa.resources` explicitly.
2 changes: 1 addition & 1 deletion charts/sombra/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ apiVersion: v2
name: sombra
description: A Helm chart to deploy Sombra and its dependent services in a Kubernetes cluster
type: application
version: 0.13.0
version: 0.14.0
maintainers:
- name: Transcend
email: dev@transcend.io
Expand Down
8 changes: 4 additions & 4 deletions charts/sombra/tests/deployment_test.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -318,11 +318,11 @@ tests:
path: spec.template.spec.containers[1].resources
value:
limits:
cpu: 100m
memory: 128Mi
cpu: 500m
memory: 1Gi
requests:
cpu: 50m
memory: 64Mi
cpu: 250m
memory: 512Mi
- notExists:
path: spec.template.spec.containers[1].lifecycle
- contains:
Expand Down
13 changes: 7 additions & 6 deletions charts/sombra/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -298,15 +298,16 @@ opa:
# keep `--addr` in sync when changing this value.
port: 8181

# Resource requests and limits for the OPA container. Defaults are
# intentionally conservative; tune from load-test data.
# Resource requests and limits for the OPA container. Requests match the
# ECS opa-mts Fargate reservation (cpu=256 / memory=512); limits give the
# sidecar 2x headroom to burst. Tune from load-test data.
Comment thread
Utsav-Patel marked this conversation as resolved.
resources:
requests:
cpu: "50m"
memory: "64Mi"
cpu: "250m"
memory: "512Mi"
limits:
cpu: "100m"
memory: "128Mi"
cpu: "500m"
memory: "1Gi"

# Container-level security context.
securityContext: {}
Expand Down
Loading