Skip to content
This repository has been archived by the owner on Oct 16, 2024. It is now read-only.

[Feature] Please update AWS EKS add-on to support kubernetes 1.28+ #51

Closed
2 tasks done
rbudiharso opened this issue Feb 6, 2024 · 3 comments
Closed
2 tasks done

[Feature] Please update AWS EKS add-on to support kubernetes 1.28+ #51

rbudiharso opened this issue Feb 6, 2024 · 3 comments
Assignees
@chipzoller
Labels
enhancement New feature or request

Comments

@rbudiharso
Copy link

Problem Statement

The AWS EKS add-on for kubecost only support kubernetes version up to 1.27, in the mean time AWS EKS already support k8s 1.28 and 1.29. Please add support for 1.28+

Solution Description

Add support for k8s 1.28+ on AWS EKS add-on

Alternatives

No response

Additional Context

No response

Troubleshooting

  • I have read and followed the issue guidelines and this is a feature request only for the Kubecost application.
  • I have searched other issues in this repository and mine is not recorded.
@rbudiharso rbudiharso added enhancement New feature or request needs-triage A label added by default to all issues indicating it needs to be curated and triaged internally. labels Feb 6, 2024
@rbudiharso rbudiharso changed the title [Feature] AWS EKS add-on doesn't support kubernetes 1.28+ [Feature] Please update AWS EKS add-on to support kubernetes 1.28+ Feb 6, 2024
@jessegoodier
Copy link

@chipzoller, is this something you can look at?

@chipzoller chipzoller self-assigned this Feb 7, 2024
@chipzoller chipzoller removed the needs-triage A label added by default to all issues indicating it needs to be curated and triaged internally. label Feb 7, 2024
@chipzoller
Copy link
Collaborator

Sent aws-samples/eks-anywhere-addons#208 to bump the add-on to v2.0.2.

@chipzoller
Copy link
Collaborator

2.0.2 should now be available.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@chipzoller chipzoller

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rbudiharso @chipzoller @jessegoodier