Bump sigs.k8s.io/external-dns from 0.16.1 to 0.17.0

[dependabot]

Bumps sigs.k8s.io/external-dns from 0.16.1 to 0.17.0.

Release notes

Sourced from sigs.k8s.io/external-dns's releases.

v0.17.0

Global information

ℹ️ On Pi Hole, support for v6 has been added. Pi Hole v5 support is deprecated and will be removed in a future version

ℹ️ On OVH, the provider has been heavily rewritten. New ACLs are need. See documentation and PR #5143 for details.

ℹ️ On IPv6, the proposal 002 has been implemented, thanks to @​hjoshi123

• ⚠️ In the next release, the default of this new expose-internal-ipv6 flag will be set to false

⚠️ There is a severe known issue with Active Directory (#5240) since v0.16.0. PR to fix it (#5385) is in review

ℹ️ The legacy txt-format will be removed in the next minor version (#5172)

• ⚠️ There is currently no migration script to clean old style txt records. If you need it, if you think you can do it, PRs are welcome.

ℹ️ A new Nomad source may be added to external-dns (#5284)

• This PR can be merged only after a review and test from real Nomad users

🚀 Features

• feat: additional template functions by @​matkam in #3949
• feat(banner): standardize user agent and output by @​ivankatliarchuk in #5154
• feat(chart): Update image to v0.16.1 by @​stevehipwell in #5201
• feat(cloudflare): multiple custom hostnames support by @​mrozentsvayg in #5239
• feat(helm): allow extraArgs to also be a map enabling overrides of individual values by @​frittentheke in #5293
• feat: IDNA awareness in the zone finder by @​lexisother in #5147
• feat(ovh): major rewriting of the provider by @​rbeuque74 in #5143
• feat(pihole): add optional support for v6 by @​tJouve in #5226
• feat(pihole): add support for IPv6 Dual format by @​tJouve in #5253
• feat(source): optional exclusion of unschedulable nodes by @​Hayajiro in #5045
• feat(source): optional expose of nodes internal ipv6 by @​hjoshi123 in #5192

🐛 Bug fixes

• fix(aws): typo on route53 IAM by @​tico24 in #5197
• fix(chart): add missing types for empty values by @​t3mi in #5207
• fix(cloudflare): custom hostnames edge-cases causing duplicates by @​mrozentsvayg in #5183
• fix(cloudflare): regional hostnames by @​vflaux in #5175
• fix(Gateway API): ensure generation match by @​davidwin93 in #5241
• fix(gateway-api): ensure to use only latest generation with HTTPRoutes by @​kashalls in #5349
• fix(helm): added missing schema values by @​ivankatliarchuk in #5228
• fix(helm): update helm schema by @​semnell in #5297
• fix(log testing): re-use logger library testing functionality by @​ivankatliarchuk in #5368
• fix(node): logger test fixed by @​ivankatliarchuk in #5232
• fix(ovh): handling capitalized DNS records + prevent panic by @​rbeuque74 in #5390
• fix(webhook): api json object plan.Changes case by @​ivankatliarchuk in #5355
• fix(zonefinder): handle underscores in dns records by @​arthlr in #5281

📝 Documentation

... (truncated)

Changelog

Sourced from sigs.k8s.io/external-dns's changelog.

Release

Release cycle

Currently we don't release regularly. Whenever we think it makes sense to release a new version we do it. You might want to ask in our Slack channel external-dns when the next release will come out.

Staging Release cycle

A new staging image is released weekly and can be found at gcr.io/k8s-staging-external-dns/external-dns.

There is a time lag between merging changes into the master branch and the subsequent creation of the staging image.

Example command to fetch 10 most recent staging images:

export EXT_DNS_VERSION="v0.17.0"
curl -sLk https://gcr.io/v2/k8s-staging-external-dns/external-dns/tags/list | jq | grep "$EXT_DNS_VERSION" | tail -n 10

Versioning convention

These are the conventions that we will be using for releases following 0.7.6:

• Patch version should be updated if we need to merge bugfixes, e.g. provider a does need a fix in order make updates working again. I would see updating or improving documentation here.

• Minor version should be updated if new features are implemented in existing providers or new provider get introduced.

• Major version should be upgraded if we introduce breaking changes.

How to release a new image

Prerequisite

We use https://github.com/cli/cli to automate the release process. Please install it according to the official documentation.

You must be an official maintainer of the project to be able to do a release.

Steps

• Run scripts/releaser.sh to create a new GitHub release. Alternatively you can create a release in the GitHub UI making sure to click on the autogenerate release node feature.
• The step above will trigger the Kubernetes based CI/CD system Prow. Verify that a new image was built and uploaded to gcr.io/k8s-staging-external-dns/external-dns.
• Create a PR in the k8s.io repo by taking the current staging image using the sha256 digest. They can be obtained with scripts/get-sha256.sh. Once the PR is merged, the image will be live with the corresponding tag specified in the PR.
  • See kubernetes/k8s.io#540 for reference
• Verify that the image is pullable with the given tag
  • docker run registry.k8s.io/external-dns/external-dns:v0.16.0 --version
• Branch out from the default branch and run scripts/version-updater.sh to update the image tag used in the kustomization.yaml and in documentation.
• Create the PR with this version change.
• Create an issue to release the corresponding Helm chart via the chart release process (below) assigned to a chart maintainer
• Once the PR is merged, all is done :-)

... (truncated)

Commits

• 7e9f148 Merge pull request #5394 from mloiseleur/feat/release-emojis-title
• 1502f0f Merge pull request #5390 from rbeuque74/ovh-sigsegv
• 39def3f fix: ovh: handling capitalized DNS records + prevent panic
• 54fc939 chore(github): add a release template (#5324)
• 346095b chore(ci): improve release script
• 2f089bd Merge pull request #5304 from gofogo/feat-code-cleanup-01
• df28bbe Merge pull request #5388provider/zone-id-filter#5150
• 68b1cdb chore(source): code cleanup
• ec8e95d imp: improved test coverage from 66.7 to 100%
• f08289d feat: additional template functions (#3949)
• 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)