Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] CoreDNS out of date/support/recommendation #7002

Closed
AndrewFarley opened this issue Aug 26, 2023 · 2 comments · Fixed by #7178
Closed

[Bug] CoreDNS out of date/support/recommendation #7002

AndrewFarley opened this issue Aug 26, 2023 · 2 comments · Fixed by #7178
Assignees
Labels
kind/bug priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases

Comments

@AndrewFarley
Copy link

AndrewFarley commented Aug 26, 2023

What were you trying to accomplish?

Deploying/updating an EKS cluster via EKSCTL and installing the "utils" supported. Unfortunately, the embedded coredns versions/builds for every supported version of EKS are out of date according to Amazon's documentation on recommended CoreDNS versions.

Reference: https://docs.aws.amazon.com/eks/latest/userguide/managing-coredns.html#coredns-versions

EDIT Sep 13 Updated versions from URL

@Himangini
Copy link
Collaborator

Related to #6999 Update aws-node workflow needs to be fixed

@Himangini
Copy link
Collaborator

Spike to understand how much work is involved with automation pov
Outcome - document findings here
Timebox - 1-2 days

@Himangini Himangini added the priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases label Sep 12, 2023
@TiberiuGC TiberiuGC self-assigned this Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants