Support cluster-api MachineDeployments
- Dominant language
- Go
- Stars
- 16.7k
- Forks
- 4.7k
- Avg merge
- 17h 21m
- Merged PRs (30d)
- 68
Description
Once we have CRDs (#6849), we should be able to support MachineDeployments for Nodes with kops. This should enable e.g. better interaction with the cluster autoscaler, or (limited) dynamic manipulation of nodes without reinvoking the kops CLI.
cluster-api is still alpha, so we won't make this the default (nor even required for the foreseeable future).
This feature is purely for tackling non-master Nodes; master nodes are much more complex; they also might not be as useful to manage through cluster-api (in my opinion).
Contributor guide
Research direction
Start with the CRDs from #6849 and the existing kops handling for non-master Nodes. Define how MachineDeployments should interact with the cluster autoscaler and dynamic node changes without making cluster-api required or the default. Done means non-master Nodes can be managed through MachineDeployments while master-node management remains out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100