Upgrading core dns self managed addon will have downtime ?
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
Hello everyone, just want to know if upgrading EKS self-managed codeDNS will have downtime ?
Our EKS cluster is in 1.23 version and coreDNS is v1.8.4-eksbuild.1. We want to upgrade coreDNS to v1.8.7-eksbuild.3.
The upgrade doc which we have followed for previous versions: [](https://docs.aws.amazon.com/eks/latest/userguide/managing-coredns.html)
Can you please tell me, whether this upgrade will cause any downtime for the cluster and applications in it?
Contributor guide
Research direction
Start with the linked AWS EKS managing CoreDNS documentation and the upgrade guidance for Kubernetes 1.23, CoreDNS v1.8.4-eksbuild.1, and v1.8.7-eksbuild.3. Confirm the expected downtime behavior and update or clarify the documentation so users can understand the impact on their cluster and applications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100