AWS EKS with Cluster of Locally Physical Machines
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
I'm new to AWS EKS and it seems very useful for our production line. We want to figure if we can use it with our architecture or not.
We need to set up the Kubernetes Master using AWS EKS to make use of all its features, and we need the master node to be on an EC2 instance but we do not want to use workers(slave nodes) on EC2 instances because we already have a cluster of a few locally physical machines with different architectures.
We think AWS EKS will offer us too many advantages and we're looking forward to adding it to our system. We just need to make sure if it meets our current system architecture and if it meets we're looking for how to grab AWS EKS into our system.
Contributor guide
Research direction
The issue names AWS EKS, EC2, Kubernetes, and an existing cluster of physical machines, but no repository files, tests, or entry points. Start by clarifying whether EKS can use the described architecture and what support or documentation change is expected. Done would be a resolved feasibility decision with the required integration path documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100