-
Notifications
You must be signed in to change notification settings - Fork 578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement AWSMachinePools using ASG #1722
Comments
/priority important-longterm |
/help |
@detiber: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign |
@gab-satchi are you working on this already or plan to work on it ? when can we get this feature ? |
We're actually working on this currently as part of adding EKS Support (it should still work with the Kubeadm provider). |
/assign @mytunguyen |
Fixed in #1860 |
/kind feature
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Implement AWSMachinePool using Auto Scaling Group. The AWSMachinePool implementation should follow the same package / group structure as CAPI and be added to the
exp
package, the experimental feature package. The feature should be gated using theMachinePool
flag used in CAPI.See also: kubernetes-sigs/cluster-api-provider-azure#483 and CAPI Machine Pool Proposal
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: