Skip to content

fix: correct inaccurate rollout restart claims for CoreDNS autoscaling enablement#1231

Open
devanshpoplii wants to merge 1 commit intoawsdocs:mainlinefrom
devanshpoplii:patch-5
Open

fix: correct inaccurate rollout restart claims for CoreDNS autoscaling enablement#1231
devanshpoplii wants to merge 1 commit intoawsdocs:mainlinefrom
devanshpoplii:patch-5

Conversation

@devanshpoplii
Copy link
Copy Markdown
Contributor

Enabling CoreDNS autoscaling does not trigger a rollout restart of the CoreDNS Deployment.
It only adjusts the replica count without modifying the pod template or restarting existing pods.

This PR corrects the documentation to accurately reflect this behavior, removing references
to rollouts and pod replacement in the context of enabling autoscaling.

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Updated the documentation to clarify that Amazon EKS applies the autoscaling configuration without a rollout restart of CoreDNS pods, and adjusted the wording for clarity.
@devanshpoplii devanshpoplii requested a review from a team as a code owner March 30, 2026 17:58
@aws-amplify-us-east-1
Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-1231.d3rijirjvbh87e.amplifyapp.com

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant