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

Add EKS Control Plane Provider to clusterctl #1970

Closed
richardcase opened this issue Sep 23, 2020 · 8 comments · Fixed by kubernetes-sigs/cluster-api#3685
Closed

Add EKS Control Plane Provider to clusterctl #1970

richardcase opened this issue Sep 23, 2020 · 8 comments · Fixed by kubernetes-sigs/cluster-api#3685
Assignees
Labels
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.

Comments

@richardcase
Copy link
Member

User Story

As a user/operator] I would like clusterctl to support the EKS control plane provider so that i can init a cluster with the required providers to create EKS clusters

Detailed Description

Initially the EKS control plane was included in the main CAPA controller. However, this has now been split out into its own controller. See #1945

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue.]

/kind feature

@ncdc
Copy link
Contributor

ncdc commented Sep 24, 2020

@richardcase would it make sense to transfer this issue to the CAPA repo?

@fabriziopandini
Copy link
Member

This is for adding EKS control plane to clusterctl.
/retitle Add EKS Control Plane Provider to clusterctl

@k8s-ci-robot k8s-ci-robot changed the title Add EKS Control Plane Provider Add EKS Control Plane Provider to clusterctl Sep 24, 2020
@ncdc
Copy link
Contributor

ncdc commented Sep 24, 2020

Is the full fix for this issue the PR in CAPA though?

@richardcase
Copy link
Member Author

@ncdc - Yes the full refactor in CAPA to create the separate eks control plane manager was in this PR: #1949

@ncdc
Copy link
Contributor

ncdc commented Sep 24, 2020

Sorry, I was referring to kubernetes-sigs/cluster-api#3685. Will that "fix" this issue? If so, I'd prefer to transfer this issue to CAPA, and assign it a CAPA milestone instead of a CAPI one. WDYT?

@richardcase
Copy link
Member Author

Ah, yes. That makes sense

@ncdc ncdc transferred this issue from kubernetes-sigs/cluster-api Sep 24, 2020
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 24, 2020
@ncdc
Copy link
Contributor

ncdc commented Sep 24, 2020

Transferred!

@richardcase
Copy link
Member Author

/assign
/lifecycle active

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants