Skip to content

Support EKS upgrade policy #5183

@richardcase

Description

@richardcase
Member

/kind feature

Describe the solution you'd like

Currently when creating an EKS cluster using CAPA there is no way to set the upgrade policy. This means the default of "extended" is used that means thate lcuster will automatically enter extended support (with the extra cost that entails).

There is no way to specify "standard" as the upgrade policy with CAPA.

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):

Activity

added
kind/featureCategorizes issue or PR as related to a new feature.
needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.
on Oct 25, 2024
richardcase

richardcase commented on Oct 25, 2024

@richardcase
MemberAuthor

/assign
/lifecycle active

added
lifecycle/activeIndicates that an issue or PR is actively being worked on by a contributor.
on Oct 25, 2024
richardcase

richardcase commented on Oct 25, 2024

@richardcase
MemberAuthor

/triage accepted

added
triage/acceptedIndicates an issue or PR is ready to be actively worked on.
and removed
needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.
on Oct 25, 2024
nalum

nalum commented on Jan 22, 2025

@nalum

I'm interested in taking a look at this

richardcase

richardcase commented on Jan 22, 2025

@richardcase
MemberAuthor

/unassign
/assign Nalum

linked a pull request that will close this issue on Apr 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.lifecycle/activeIndicates that an issue or PR is actively being worked on by a contributor.needs-prioritytriage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    Participants

    @richardcase@nalum@k8s-ci-robot

    Issue actions

      Support EKS upgrade policy · Issue #5183 · kubernetes-sigs/cluster-api-provider-aws