# yaml-language-server: $schema=https://atmos.tools/schemas/atmos/atmos-manifest/1.0/atmos-manifest.json

# A local Kubernetes emulator (k3s) as a stack-scoped Atmos component.
# `atmos emulator up kubernetes -s <stack>` starts (or reuses) the privileged k3s
# container. Helmfile has no Atmos Auth integration, so instead of an identity this
# example consumes the emulator declaratively: the `!emulator kubernetes kubeconfig`
# YAML function (see the dev stack's `env`) harvests the admin kubeconfig to a file
# and points KUBECONFIG at it. k3s runs privileged (a driver default); under a
# rootless runtime the manager swaps in the cgroup-nesting entrypoint automatically.
components:
  emulator:
    kubernetes:
      driver: k3s
      # Run as a throwaway cluster (no persisted state across down/up). This keeps
      # the demo cross-platform: k3s's embedded datastore creates a unix socket in
      # its data dir, and persisting that dir via a host bind-mount fails on macOS
      # (Docker/Podman virtiofs rejects `chmod` on the socket). A fresh cluster on
      # each `up` is exactly what a demo wants anyway.
      ephemeral: true