Skip to content

chore: align default resources with upstream kubeadm CoreDNS defaults#257

Open
mloza-tc wants to merge 1 commit intocoredns:masterfrom
mloza-tc:align-resources-with-kubeadm
Open

chore: align default resources with upstream kubeadm CoreDNS defaults#257
mloza-tc wants to merge 1 commit intocoredns:masterfrom
mloza-tc:align-resources-with-kubeadm

Conversation

@mloza-tc
Copy link
Copy Markdown

@mloza-tc mloza-tc commented Apr 2, 2026

Update resource requests and limits in values.yaml to match the values used by kubeadm in manifests.go(1)

  • Remove CPU limit (kubeadm does not set one, avoids DNS throttling)
  • Set memory limit to 170Mi (was 128Mi)
  • Set memory request to 70Mi (was 128Mi)

Bump chart version to 1.45.3 and add changelog entry.

Why is this pull request needed and what does it do?

The default resource requests and limits diverge from what kubeadm provisions when deploying CoreDNS as a cluster addon. This PR aligns them with the upstream values defined in manifests.go (1)

(1) https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/phases/addons/dns/manifests.go#L103-L108

Which issues (if any) are related?

N/A

Checklist:

  • I have bumped the chart version according to versioning.
  • I have updated the chart changelog with all the changes that come with this pull request according to changelog.
  • Any new values are backwards compatible and/or have sensible default.
  • I have signed off all my commits as required by DCO.

Update resource requests and limits in values.yaml to match the values
used by kubeadm in manifests.go (L103-108):
- Remove CPU limit (kubeadm does not set one; avoids DNS throttling)
- Set memory limit to 170Mi (was 128Mi)
- Set memory request to 70Mi (was 128Mi)

Bump chart version to 1.45.3 and add changelog entry.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.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