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

v1beta3 API Changes

Open richardcase opened this issue 2 years ago • 12 comments

/kind refactor /kind api-change /priority important-soon /triage accepted

Describe the solution you'd like

An issue to track the API changes that are required in the next API version bump.

Changes:

  • [ ] Removal of deprecated fields from AWSManagedMachinePool (as a result of the launch template work)
  • [ ] https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/3243

Anything else you would like to add:

This captures some changes that didn't make it into v1beta2 (v2.0.0) from #2355

### Tasks
- [ ] https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/1166
- [ ] The IamInstanceProfile property on AWSLaunchTemplates should be changed to IAMInstanceProfile (capital IAM) to be consistent with the same property on AWSMachineSpec and Go style guidelines on acronyms.  See: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/3586b3b25153ad525119199dfc9544b69ad0d15f/exp/api/v1beta2/types.go
- [ ] https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/4333

richardcase avatar Nov 15 '22 16:11 richardcase

Also #3243

Ankitasw avatar Nov 15 '22 16:11 Ankitasw

Also #3243

Added to the list

richardcase avatar Nov 15 '22 18:11 richardcase

The IamInstanceProfile property on AWSLaunchTemplates should be changed to IAMInstanceProfile (capital IAM) to be consistent with the same property on AWSMachineSpec and Go style guidelines on acronyms.

See: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/3586b3b25153ad525119199dfc9544b69ad0d15f/exp/api/v1beta2/types.go

AverageMarcus avatar Nov 24 '22 13:11 AverageMarcus

Also #1166

Ankitasw avatar Dec 05 '22 06:12 Ankitasw

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 Mar 05 '23 06:03 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 Jun 03 '23 06:06 k8s-triage-robot

/remove-lifecycle stale

richardcase avatar Jun 05 '23 08:06 richardcase

As discussed today during the office hours, here is the issue for the AZs support in VPCSpec: #4333

synthe102 avatar Jun 12 '23 17:06 synthe102

Also remove InstanceType from AWSManagedMachinePool - see https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4358

richardcase avatar Jun 28 '23 08:06 richardcase

Support for multiple load balancers as a slice/list; an improvement over #4554

nrb avatar Jan 22 '24 17:01 nrb

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 Apr 21 '24 18:04 k8s-triage-robot

/remove-lifecycle stale

richardcase avatar Apr 22 '24 15:04 richardcase

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 Jul 21 '24 15:07 k8s-triage-robot

/remove-lifecycle stale

nrb avatar Jul 22 '24 16:07 nrb

/lifecycle frozen

richardcase avatar Jul 23 '24 06:07 richardcase