cluster-api-provider-aws icon indicating copy to clipboard operation
cluster-api-provider-aws copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Add AWSManagedControlPlaneTemplate type

Open sedefsavas opened this issue 3 years ago • 20 comments
trafficstars

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

sedefsavas avatar Feb 07 '22 22:02 sedefsavas

/assign

pydctw avatar Feb 08 '22 00:02 pydctw

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

pydctw avatar Feb 23 '22 16:02 pydctw

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar May 24 '22 17:05 k8s-triage-robot

/remove-lifecycle stale

sedefsavas avatar Jun 07 '22 17:06 sedefsavas

/milestone clear

richardcase avatar Jul 25 '22 16:07 richardcase

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Oct 23 '22 18:10 k8s-triage-robot

/remove-lifecycle stale

richardcase avatar Oct 25 '22 00:10 richardcase

/milestone v2.x

richardcase avatar Nov 10 '22 17:11 richardcase

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?

richardcase avatar Nov 10 '22 17:11 richardcase

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.

pydctw avatar Nov 12 '22 01:11 pydctw

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:

  • Confirm that this issue is still relevant with /triage accepted (org members only)
  • Deprioritize it with /priority important-longterm or /priority backlog
  • Close this issue with /close

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

/remove-triage accepted

k8s-triage-robot avatar Feb 10 '23 04:02 k8s-triage-robot

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

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

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar May 11 '23 05:05 k8s-triage-robot

/remove-lifecycle stale

richardcase avatar May 15 '23 07:05 richardcase

/assign /lifecycle active

richardcase avatar Nov 25 '23 07:11 richardcase

/triage accepted

richardcase avatar Nov 25 '23 07:11 richardcase

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:

  • Confirm that this issue is still relevant with /triage accepted (org members only)
  • Deprioritize it with /priority important-longterm or /priority backlog
  • Close this issue with /close

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

/remove-triage accepted

k8s-triage-robot avatar Feb 23 '24 08:02 k8s-triage-robot

/triage accepted

richardcase avatar Feb 23 '24 14:02 richardcase