Bump sigs.k8s.io/external-dns from 0.18.0 to 0.19.0

[dependabot]

Bumps sigs.k8s.io/external-dns from 0.18.0 to 0.19.0.

Release notes

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

v0.19.0

General information

• ℹ️ CLI flags allows to set behavior of previous version on the two breaking changes included in this release, if needed.
• ℹ️ Thanks to @​valerian-roche, this version can reduce the average memory usage by ~10 times, see #5596

⚠️ Breaking Changes

• feat(nodes)!: expose external ipv6 by default by @​mloiseleur in #5575
• feat(traefik)!: disable legacy listeners on traefik.containo.us API Group by @​mloiseleur in #5565

🚀 Features

• feat(aws): add support for ap-east-2 by @​chemi0213 in #5638
• feat(aws): add support for geoproximity routing by @​prasadkatti in #5347
• feat(azure): update Azure provider configuration and documentation by @​antchand in #5648
• feat(chart): add option to configure annotationFilter via dedicated helm value by @​dshatokhin in #5737
• feat(events): raise k8s events with fake provider by @​ivankatliarchuk in #5659
• feat(metrics): publish build_info metric by @​ivankatliarchuk in #5643
• feat(nodes)!: expose external ipv6 by default by @​mloiseleur in #5575
• feat(source/istio): support version 1.25+ by @​ivankatliarchuk in #5611
• feat(source/pods): support for annotation and label filter by @​ivankatliarchuk in #5583
• feat(source): support --event flags with sources pod and node by @​ivankatliarchuk in #5642
• feat(source): use transformers in pod informers to reduce memory footprint by @​valerian-roche in #5596
• feat(traefik)!: disable legacy listeners on traefik.containo.us API Group by @​mloiseleur in #5565

🐛 Bug fixes

• fix(api): rollback oas and update linter by @​ivankatliarchuk in #5723
• fix(aws): support aws_ca_bundle by @​mwmix in #5665
• fix(chart): Change .extraContainers type to array by @​svengreb in #5564
• fix(cloudflare): display of action in logs by @​vflaux in #5550
• fix(cloudflare): set comments properly by @​7onn in #5582
• fix(cloudflare): unnecessary record updates by @​vflaux in #5770
• fix(controller): panic in events.Controller.Add() by @​vflaux in #5766
• fix(docs): Fixing some errors in the dev-guide example. by @​mwmix in #5662
• fix(endpoint): domains handling with idna by @​ivankatliarchuk in #5685
• fix(helm): resolve RBAC permissions for namespaced gateway sources by @​u-kai in #5578
• fix(helm): Update helm value schema to allow create-only policy type by @​coltonhughes in #5627
• fix(http): concurrent map read/write by @​ivankatliarchuk in #5753
• fix(instrumented_http): migrate to own http instrumenter by @​ivankatliarchuk in #5650
• fix(metrics): make prometheus labels more type safe by @​mwmix in #5717
• fix(oas): add required properties to api components by @​evilhamsterman in #5696
• fix(pihole): create record for all targets by @​vkolobara in #5584
• fix(provider/aws): null pointer when records mailformed by @​ivankatliarchuk in #5639
• fix(provider/aws-sd): fix namespace type filtering by @​ivankatliarchuk in #5682
• fix(provider): IDNA awareness in the zone finder by @​hanapedia in #5705
• fix(rbac): conditional endpointslices perms by @​vflaux in #5746
• fix: reduce warning by using idna profile by @​szuecs in #5587
• fix(rfc2136): Use correct index for accessing UpdateOld if there are multiple chunks by @​schwajo in #5542

... (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.19.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#8466 for reference
• Verify that the image is pullable with the given tag
  • docker run registry.k8s.io/external-dns/external-dns:v0.x.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

• eafce22 fix: typo (#5787)
• 3861441 fix(cloudflare): unneeded records updates (#5770)
• fe142a8 fix(source/crd): increase tests timeouts (#5785)
• c6ed951 fix(txt-registry): skip creation of already-existing TXT records (#4914) (#5459)
• 8cf6e42 docs: add new webhook provider SAKURA Cloud into README (#5784)
• e78b385 chore(cloudflare): migrate CreateDNSRecord() to new lib (#5779)
• 5181b3f chore(cloudflare): migrate DNSRecord to new lib struct (#5762)
• 9e0acd0 feat(azure): update Azure provider configuration and documentation (#5648)
• 07ae419 chore(deps): bump the dev-dependencies group across 1 directory with 2 update...
• cff8d0d fix(doc): typo in compatibility table (#5769)
• 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)