maximilien / maximilien/weave-cli
feat: EKS Support (AWS) - Cloud Deployment
Open
Nobody has claimed this yet.
enhancement
feature
p1
phase-2
- Dominant language
- Go
- Stars
- 34
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Implement AWS EKS support for production cloud deployments as part of Phase 2.
Scope
- Update weave-stack.yaml schema for EKS config
- Implement EKS cluster creation (src/pkg/stack/eks.go)
- Add EKS-specific Helm values (LoadBalancer, EBS, IAM)
- Test EKS deployment end-to-end
- Document EKS setup and configuration
Commands
weave stack up --runtime eks
Success Criteria
- EKS deployment tested on real AWS account
-
weave stack up --runtime eksworks - EKS setup guide complete
Priority: Phase 2 - Week 1
Estimated: 3-4 days
Assignee: TBD (looking for Engineer with AWS/K8s experience)
Related
Part of Phase 2 cloud deployment push. Pairs with GKE support.
Contributor guide
No contributing guide indexed for this repository
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 reviewing weave-stack.yaml and src/pkg/stack/eks.go, then trace how weave stack up --runtime eks selects a runtime. Check the existing Helm values and related GKE support for the required LoadBalancer, EBS, and IAM configuration. Done means a real AWS EKS deployment works, the command succeeds, and the setup guide is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, helm, kubernetes
- Domain
- cli, cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100