---
id: resources-on
name: "Capability: resource requests/limits set on ALL workloads (ON)"
description: >-
  Renders the product chart with resources.requests and resources.limits
  configured (cpu=100m memory=128Mi / cpu=500m memory=256Mi) and asserts
  that every workload container carries the configured resources block.
  The scope and darkroom templates wire {{- with .Values.resources }} but
  the skywatcher Deployment does NOT include a resources block — setting
  resources has no effect on skywatcher. Scope and darkroom are not enabled
  in this scenario due to a pre-existing chart bug (scope readiness probe
  mismatch), but the skywatcher gap alone makes this scenario EXPECTED to
  FAIL (honest red gap). Scope and darkroom WOULD honor resources if enabled.
labels: {customer: enterprise, profile: compliance}
cluster:
  provider: kind
  k8s_version: v1.36.1
product:
  chart: ./chart
  release: sample
  namespace: sample
  set:
    resources.requests.cpu: 100m
    resources.requests.memory: 128Mi
    resources.limits.cpu: 500m
    resources.limits.memory: 256Mi
asserts:
  - type: resources-present
    namespace: sample
    source: rendered
    expect_present: true
    requests:
      cpu: 100m
      memory: 128Mi
    limits:
      cpu: 500m
      memory: 256Mi
tags: [capability, compliance]
category: capability
capability: resource-limits
tier: capability
mechanisms: ["capability:resources"]