Skip to content
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

Closed
CecileRobertMichon opened this issue May 13, 2020 · 8 comments
Closed

Implement AWSMachinePools using ASG #1722

CecileRobertMichon opened this issue May 13, 2020 · 8 comments
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone

Comments

@CecileRobertMichon
Copy link

/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 the MachinePool 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:

  • Cluster-api-provider-aws version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label May 13, 2020
@detiber detiber added this to the Next milestone May 18, 2020
@detiber
Copy link
Member

detiber commented May 18, 2020

/priority important-longterm

@k8s-ci-robot k8s-ci-robot added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label May 18, 2020
@detiber
Copy link
Member

detiber commented May 18, 2020

/help

@k8s-ci-robot
Copy link
Contributor

@detiber:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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.

@k8s-ci-robot k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label May 18, 2020
@gab-satchi
Copy link
Member

/assign

@krmayankk
Copy link

@gab-satchi are you working on this already or plan to work on it ? when can we get this feature ?

@rudoi
Copy link
Contributor

rudoi commented Aug 5, 2020

We're actually working on this currently as part of adding EKS Support (it should still work with the Kubeadm provider).

@gab-satchi gab-satchi removed their assignment Aug 5, 2020
@randomvariable
Copy link
Member

/assign @mytunguyen
/lifecycle active

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Aug 14, 2020
@randomvariable randomvariable modified the milestones: Next, v0.6.1 Aug 14, 2020
@randomvariable randomvariable modified the milestones: v0.6.1, v0.6.2 Sep 30, 2020
@randomvariable
Copy link
Member

Fixed in #1860

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

8 participants