# design 7 C-G2: grey zone, container. StressChaos memory on api pods; latency rises, intermittent 5xx. Correct: k8s.rollout_restart after approval.
id: C-G2
path: gray
asset: container
expected_layer: 2
ground_truth_label: memory_pressure_api
ground_truth_action: k8s.rollout_restart
description: StressChaos memory workers 2 size 225MB (api limit 256Mi, working set about 0.9), app=api, duration 10m
notes:
  open_item: "design 11.3: whether the stress re-attaches to the restarted pods for the remaining duration"
inject:
  method: chaos
  manifest: |
    apiVersion: chaos-mesh.org/v1alpha1
    kind: StressChaos
    metadata:
      namespace: chaos-mesh
    spec:
      mode: all
      selector:
        namespaces: [demo]
        labelSelectors:
          app: api
      stressors:
        memory:
          workers: 2
          # 2026-10-08: "80%" is a share of the node memory (memStress reached 4.4 GB), so the cgroup OOM killer took memStress
          # and the api process within a second: one restart per pod, no sustained pressure, no alert. 200MB stays under the
          # 256Mi limit. 200MB left the working set at 0.797-0.803 of the limit (campaign 3), flapping around the 0.8
          # threshold; 225MB keeps it near 0.9 so ApiMemoryPressure holds.
          size: "225MB"
      duration: "10m"
revert:
  method: chaos_delete