Skip to content

Support EKS upgrade policy #5183

@richardcase

Description

@richardcase

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

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

No branches or pull requests

Issue actions