Skip to content

docs: clarify CoreDNS version is tied to plugin.cfg#30

Merged
davidpoblador merged 1 commit intomainfrom
fix/honest-coredns-version-pinning
Apr 4, 2026
Merged

docs: clarify CoreDNS version is tied to plugin.cfg#30
davidpoblador merged 1 commit intomainfrom
fix/honest-coredns-version-pinning

Conversation

@davidpoblador
Copy link
Copy Markdown
Member

Summary

  • Add a comment in the Dockerfile explaining that COREDNS_VERSION must match the upstream version plugin.cfg is based on
  • Replace the misleading "Build arguments" README section (which implied COREDNS_VERSION was freely overridable) with an "Upgrading versions" section that documents the correct upgrade procedure
  • Update the example --build-arg command to show COREDNS_TAILSCALE_VERSION (the one that actually can be overridden independently)

Closes #22

Test plan

  • Verify README links (#upgrading-versions anchor) render correctly on GitHub
  • Confirm no functional changes to the Docker build

🤖 Generated with Claude Code

The COREDNS_VERSION build arg is not freely overridable because
plugin.cfg is version-specific and checked in. Update the Dockerfile
with a comment explaining the coupling, and replace the misleading
"Build arguments" README section with upgrade instructions.

Closes #22

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@davidpoblador davidpoblador merged commit dfd5a18 into main Apr 4, 2026
1 check passed
@davidpoblador davidpoblador deleted the fix/honest-coredns-version-pinning branch April 4, 2026 22:38
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.

Make CoreDNS version pinning honest now that plugin.cfg is checked in

1 participant