--provider aws-eks. The generic Kubernetes requirements apply unchanged; this page is the delta and how far the evidence goes.
Status
Provider profile implemented; not yet validated by a station run in a real EKS cluster.kit/providers/aws-eks/profile.env carries PROFILE_TESTED=no, and the installer prints that on every run — this profile is declared, not yet exercised end-to-end; expect deltas. The deltas below are named from AWS documentation, not measured by us. The first subscriber on EKS validates this page: the preflight, smoke and station reports from that install are the evidence, and this line changes when they exist.
What the provider profile configures
install.sh has no per-provider branches — provider differences live only in kit/providers/<name>/profile.env. The aws-eks file sets the same pinned versions every profile sets, Argo CD v3.5.1 and Kyverno v1.19.0, and nothing else. It installs no addon, selects no storage class and writes no load-balancer annotation. Those are your cluster’s own configuration. Preflight checks the storage class (P8) and the pull path to the channel (P5, P7); it reads no load-balancer or ingress state at all, so that row is yours to confirm.
What the cluster must provide
Next: Install · Preflight · Kubernetes