feat(provider): EKS managed-cluster provider (mock-first)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 30
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Add an EKS provider using the interface-fake pattern proven in #844: consumer-defined interfaces over aws-sdk-go-v2/service/eks, a stateful FakeEKS extending internal/aws/awsfake (waiter-compatible state transitions, exact error codes, error injection, call recorder), and mock E2E driving real orchestration.
CI already holds AWS credentials — real validation is an IAM-policy expansion on the existing account, gated behind a new real-eks label family (1 job/PR cap, matching the #844 CI shape).
Blocked on the Provider-abstraction decision: EKS is a managed control plane that skips the SSH-provisioner phase, so the Provider model needs a capability model or a parallel ManagedCluster path — design discussion happens before any implementation task is cut.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the interface-fake pattern in #844 and the existing Provider abstraction, then review internal/aws/awsfake for the state and error behavior this issue names. Resolve whether the Provider model gains capabilities or a parallel ManagedCluster path; the work is ready only after that decision and a concrete implementation task are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100