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

[dependabot]

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

Release notes

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

v0.16.1

This release fixes the breaking change introduced in v0.16.0 for Cloudflare.

⚠️ New features on Cloudflare, custom and regional hostnames have some known issues, see #5175 and #5183

⚠️ OpenStack designate in-tree provider will be removed in the next version. There is now a webhook provider.

ℹ️ With v0.16.0, a new option on TXT Registry is available to use only new format (#4946). Previous format will be removed in the next release (#5172).

🐛 Bug fixes

• fix(cloudflare): optional custom hostnames by @​mrozentsvayg in kubernetes-sigs/external-dns#5146
• fix(source): pass GatewayName to config by @​buroa in kubernetes-sigs/external-dns#5169
• fix(cloudflare): infinite loop with more than 50 custom hostnames by @​mrozentsvayg in kubernetes-sigs/external-dns#5181

📦 Others

• chore: update OWNERS with required config file by @​mloiseleur in kubernetes-sigs/external-dns#5164

Full Changelog: kubernetes-sigs/external-dns@v0.16.0...v0.16.1

v0.16.0

💥 Breaking Changes

There is a breaking change on Cloudflare with this release. It requires Cloudflare for Saas.

🚀 Features

• feat: add dreamhost webook provider to readme (#5015) @​asymingt
• feat: Add F5 TransportServer source (#4944) @​visokoo
• feat(chart): allow to run tpl on ServiceAccount annotations (#4958) (#4958) @​fcrespofastly
• feat(cloudflare): custom hostname and fix apex (#5087) @​mrozentsvayg
• feat(deps): added renovate config for custom regexes (#4978) @​ivankatliarchuk
• feat: don't discard klog logs at the highest log levels (debug and trace) (#4961) @​dmarkhas
• feat(pdns): add validation for MX and SRV records (#4871) @​julillae
• feat(rfc2136): support multiple hosts (#4653) @​Jeremy-Boyle
• feat(service): listen to endpoint changes (#5085) @​dmarkhas
• feat(source): allow to register all pods and their associated PTR record (#4782) @​foyerunix
• feat(txt-registry): add option to use only new format (#4946) @​malpou

🐛 Bug fixes

• fix(aes-encryption): support plain txt and url safe base64 strings (#4980) @​ivankatliarchuk
• fix(aws-provider): ListTagsForResource incorrect zone-id handling (#5029) @​ivankatliarchuk
• fix(chart): non-string types on svcaccount annotations (#5067) @​hjoshi123
• fix(chart): regression with affinity.nodeAffinity getting ignored (#5046) @​mkhpalm
• fix(chart): update rbac for F5 transportserver source (#5066) (#5066) @​visokoo
• fix(cloudflare): add more descriptive log message (#5047) @​AndrewCharlesHay
• fix(cloudflare): use softerror on internal server error with api (#4931) @​vishuvenu
• fix(dedup): records with different type are not duplicates (#4889) @​jtszalay

... (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.16.1"
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

• 017f768 fix(cloudflare): infinite loop with more than 50 custom hostnames (#5181)
• 69da80f Merge pull request #5169 from buroa/master
• a624332 fix(source): config didnt set gatewayname
• 44f1008 cloudflare: bugfix - do not attempt to create unconfigured empty custom hostn...
• a3f4188 Merge pull request #5164 from mloiseleur/fix/owners
• 6bb785d chore: update OWNERs with left required config file
• 724b86b feat(source): fitler by gateway name (#5160)
• c72c499 Merge pull request #5158 from kubernetes-sigs/add/labels
• 5b5bd09 fix: add mexico region to external dns supported load balancers (#5157)
• 1ace1c4 add: auto label source and providers
• 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)