Antithesis K8s Onboarding Assistance

Purpose and Goal

Help customers running on Kubernetes minimize their production manifests down to a form antithesis-setup can use to construct an Antithesis test environment. The output is a structured analysis report — not modified YAML.

Success means:

• antithesis/scratchbook/k8s-minimization.md is a stable, reviewable report describing the components, dependencies, stub strategies, and decisions setup will need to construct the test environment for a k8s-based SUT
• antithesis/scratchbook/k8s-minimization-work/working.md captures the live decision history across passes — including reversals, defaulted decisions, and open assumptions
• The customer has either (a) finished work on this skill with the final report ready for setup, or (b) an escalation packet ready to share with their Antithesis engagement team

This skill applies only to customers running on Kubernetes. Customers using Docker Compose directly skip this skill and go straight from antithesis-research to antithesis-setup.

Note: antithesis-setup currently builds Docker Compose harnesses. Setup-side k8s support is a separate effort. When that effort lands, this skill's final report becomes setup's input for k8s customers; until then, the report is a structured handoff to the Antithesis engagement team rather than a direct setup input. The skill produces the same artifact regardless of which path the consumer takes downstream.

Prerequisites and Scoping

Before this skill can do useful work, it needs scope information about what's being tested: SUT identity, test boundary, and success criteria for the app running correctly.