kubernetes-sigs / cluster-api-provider-aws

Kubernetes Cluster API Provider AWS provides consistent deployment and day 2 operations of "self-managed" and EKS Kubernetes clusters on AWS.
http://cluster-api-aws.sigs.k8s.io/
Apache License 2.0
646 stars 570 forks source link

Add AWSManagedControlPlaneTemplate type #3166

Open sedefsavas opened 2 years ago

sedefsavas commented 2 years ago

Add a new CRD named AWSManagedControlPlaneTemplate, that will be used with ClusterClass.

This should have the same webhooks with AWSManagedControlPlane. (Example AWSClusterTemplate PR: https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/2585)

/kind feature

pydctw commented 2 years ago

/assign

pydctw commented 2 years ago

Adding clusterclass for EKS is blocked until we have a resolution on https://github.com/kubernetes-sigs/cluster-api/issues/6126

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

sedefsavas commented 2 years ago

/remove-lifecycle stale

richardcase commented 2 years ago

/milestone clear

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

richardcase commented 2 years ago

/remove-lifecycle stale

richardcase commented 2 years ago

/milestone v2.x

richardcase commented 2 years ago

This will be possible after v2.0.0 and specifically after #3797 merges.

@pydctw would you still like to work on this or is this something i can pick up?

pydctw commented 2 years ago

Hey @richardcase, do we plan to support ClusterClass for EKS after we re-introduce AWSManagedCluster? Asking because ClusterClass is not yet supported for MachinePool (https://github.com/kubernetes-sigs/cluster-api/issues/5991), which has more users based on my observation.

If we decide to support ClusterClass for EKS MachineDeployment flavor first, I can work on this issue.

k8s-triage-robot commented 1 year ago

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

richardcase commented 1 year ago

/remove-lifecycle stale

richardcase commented 11 months ago

/assign /lifecycle active

richardcase commented 11 months ago

/triage accepted

k8s-triage-robot commented 8 months ago

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

richardcase commented 8 months ago

/triage accepted

k8s-triage-robot commented 5 months ago

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

richardcase commented 4 months ago

/triage accepted

k8s-triage-robot commented 1 month ago

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged. Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

richardcase commented 1 week ago

/unassign /help

k8s-ci-robot commented 1 week ago

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

Guidelines

Please ensure that the issue body includes answers to the following questions:

For more details on the requirements of such an issue, please see here and ensure that they are met.

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

In response to [this](https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/3166): >/unassign >/help Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.