Bump github.com/coredns/coredns from 1.2.4 to 1.11.0

[dependabot]

Bumps github.com/coredns/coredns from 1.2.4 to 1.11.0.

Release notes

Sourced from github.com/coredns/coredns's releases.

v1.11.0

Release Highlights

• Adds support for accepting DNS connections over QUIC (doq).
• Adds CNAME target rewrites to the rewrite plugin.
• Plus many bug fixes, and some security improvements.

This release introduces the following backward incompatible changes:

• In the kubernetes plugin, we have dropped support for watching Endpoint and Endpointslice v1beta, since all supported K8s versions now use Endpointslice.
• The bufsize plugin changed its default size limit value to 1232
• Some changes to forward plugin metrics.

Brought to You By

Amila Senadheera, Antony Chazapis, Ayato Tokubi, Ben Kochie, Catena cyber, Chris O'Haver, Dan Salmon, Dan Wilson, Denis MACHARD, Diogenes Pelisson, Eng Zer Jun, Fish-pro, Gabor Dozsa, Gary McDonald, João Henri, Justin, Lio李歐, Marcos Mendez, Marius Kimmina, Ondřej Benkovský, Pat Downey, Petr Menšík, Rotem Kfir, Sebastian Dahlgren, Vancl, Vinayak Goyal, W. Trevor King, Yash Singh, Yashpal, Yong Tang, Yuheng, cui fliter, jeremiejig, junhwong, rokkiter, yyzxw

... (truncated)

Changelog

Sourced from github.com/coredns/coredns's changelog.

Makefile for releasing CoreDNS

The release is controlled from coremain/version.go. The version found there is

used to tag the git repo and to build the assets that are uploaded to GitHub.

The release should be accompanied by release notes in the notes/ subdirectory.

These are published on coredns.io. For example see: notes/coredns-1.5.1.md

Use make -f Makefile.release notes to create a skeleton notes document.

Be sure to prune the PR list a bit, not everything is worthy!

As seen in notes/coredns-1.5.1.md we want to style the notes in the following manner:

* important changes at the top

* people who committed/review code (the latter is harder to get)

* Slightly abbreviated list of pull requests merged for this release.

Steps to release, first:

1. Up the version in coremain/version.go

2. Do a make -f Makefile.doc # This has been automated in GitHub, so you can probably skip this step

3. go generate

4. Send PR to get this merged.

Then:

1. Open an issue for this release

2. In an issue give the command: /release master VERSION

Where VERSION is the version of the release - the release script double checks this with the

actual CoreDNS version in coremain/version.go

3. (to test as release /release -t master VERSION can be used.

See https://github.com/coredns/release for documentation README on what needs to be setup for this to be

automated (can still be done by hand if needed). Especially what environment variables need to be

set! This further depends on Caddy being setup and dreck running as a plugin in Caddy.

To release we run, these target from the this Makefile.release ordered like:

* make release

* make github-push

Testing this is hard-ish as you don't want to accidentally release a coredns. If not executing the github-push target

you should be fine.

Docker image creation and upload are now separate steps, because it often failed before. See the Makefile.docker for

details.

ifeq (, $(shell which curl)) $(error "No curl in $$PATH, please install") endif

NAME:=coredns

... (truncated)

Commits

• 9f4aa9d Update release note of 1.11.0 and prepare the release (#6223)
• 0e3b775 build(deps): bump gopkg.in/DataDog/dd-trace-go.v1 from 1.52.0 to 1.53.0 (#6239)
• 9680cbe build(deps): bump github.com/quic-go/quic-go from 0.35.1 to 0.37.3 (#6238)
• 8830cb6 build(deps): bump github.com/aws/aws-sdk-go from 1.44.312 to 1.44.317 (#6241)
• a2bc5ac build(deps): bump golang.org/x/crypto from 0.11.0 to 0.12.0 (#6242)
• cc7a364 [RFC-9250]: Add QUIC server support (#6182)
• b7c9d3e build(deps): bump google.golang.org/grpc from 1.56.2 to 1.57.0 (#6234)
• e2662bb update outdated blog links (#6231)
• 1f4fff7 build(deps): bump google.golang.org/api from 0.132.0 to 0.134.0 (#6233)
• c778fee build(deps): bump github.com/aws/aws-sdk-go from 1.44.300 to 1.44.312 (#6232)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #14.