svcforge/catalog.yaml

# The product catalog: what svcforge will provision, and in which sizes.
# service_type -> chart / chart_version / security / sizes{name -> replicas + resources}
#
# security: true bypasses every tenant's maintenance window for this entry. Set it for a
# CVE with a public exploit; leave it false and the bump waits for 03:00 Sunday.
services:
  elasticsearch:
    chart: bitnamilegacy/elasticsearch
    chart_version: 21.3.15
    security: false
    sizes:
      small:
        replicas: 1
        resources:
          requests:
            cpu: 250m
            memory: 1Gi
          limits:
            cpu: "1"
            memory: 2Gi
      medium:
        replicas: 3
        resources:
          requests:
            cpu: "1"
            memory: 4Gi
          limits:
            cpu: "2"
            memory: 8Gi

  redis:
    chart: bitnamilegacy/redis
    chart_version: 20.6.2
    security: false
    sizes:
      small:
        replicas: 1
        resources:
          requests:
            cpu: 100m
            memory: 256Mi
          limits:
            cpu: 500m
            memory: 512Mi
      medium:
        replicas: 3
        resources:
          requests:
            cpu: 500m
            memory: 1Gi
          limits:
            cpu: "1"
            memory: 2Gi

  postgres:
    chart: bitnamilegacy/postgresql
    chart_version: 16.4.5
    security: false
    sizes:
      small:
        replicas: 1
        resources:
          requests:
            cpu: 250m
            memory: 512Mi
          limits:
            cpu: "1"
            memory: 1Gi
      medium:
        replicas: 2
        resources:
          requests:
            cpu: "1"
            memory: 2Gi
          limits:
            cpu: "2"
            memory: 4Gi

  # --- Small services, for exercising the control plane on a cluster with no room ---------
  #
  # The three entries above are real products and size accordingly: one `elasticsearch`
  # small asks for 1Gi, and a medium asks for 4Gi across three replicas. On a test cluster
  # that is a request that never schedules, so provisioning them proves nothing about
  # svcforge and everything about the node.
  #
  # These two exist to exercise the actual loop — claim, helm install, CAS to ready, drift,
  # TTL, deprovision — in seconds and in tens of megabytes.
  #
  # Both are addressed as `oci://`, which is not cosmetic: an OCI chart is pulled by
  # reference with no `helm repo add` first. The entries above name `bitnamilegacy/<chart>`,
  # a classic repo alias that nothing in the worker image configures, so they cannot
  # actually resolve at provision time. OCI is the form that works from a bare container.

  podinfo:
    # A single small Go binary with no dependencies, no PVC and a fast image pull. The e2e
    # test provisions exactly this for the same reason.
    chart: oci://ghcr.io/stefanprodan/charts/podinfo
    chart_version: 6.7.1
    security: false
    sizes:
      small:
        replicas: 1
        resources:
          requests:
            cpu: 10m
            memory: 16Mi
          limits:
            cpu: 50m
            memory: 32Mi
      medium:
        replicas: 2
        resources:
          requests:
            cpu: 25m
            memory: 32Mi
          limits:
            cpu: 100m
            memory: 64Mi

  nginx:
    # A recognisable web server, still small. Useful when the thing being demonstrated needs
    # to look like a service someone would actually ask for.
    chart: oci://registry-1.docker.io/bitnamicharts/nginx
    chart_version: 25.0.14
    security: false
    sizes:
      small:
        replicas: 1
        resources:
          requests:
            cpu: 10m
            memory: 32Mi
          limits:
            cpu: 100m
            memory: 64Mi
      medium:
        replicas: 2
        resources:
          requests:
            cpu: 25m
            memory: 64Mi
          limits:
            cpu: 200m
            memory: 128Mi