Skip to content

chore(deps): bump sigs.k8s.io/external-dns from 0.15.1 to 0.18.0 #775

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 30, 2025

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

Release notes

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

v0.18.0

General information

⚠️ This release requires a RBAC update on endpointslices. It will be included in the next Chart release, see #5493.

⚠️ The exposed metrics has been significantly changed. You'll need to update your observability stack accordingly, see #5516

ℹ️ This release remove in-tree support for ibmcloud, tencentcloud & ultradns. Users needing those providers can use a previous version of external-dns or create a webhook-based provider.

ℹ️ The change on default-targets behavior provide a mitigation strategy, if you need it, see #5316

⚠️ Breaking Changes

🚀 Features

🐛 Bug fixes

... (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.18.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.
  • 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
  • 1a2d18f chore(deps): bump renovatebot/github-action (#5557)
  • 5a321b6 docs(traefik): public and private routing (#5559)
  • 9f16d83 feat(txt-registry): deprecate legacy txt-format (#5172)
  • 3c8f774 chore(deps): bump the dev-dependencies group across 1 directory with 2 update...
  • 68f2884 chore(deps): bump json-yaml-validate to v3.3.1 (#5563)
  • 57abe1d fix(docs): fix documentation (#5560)
  • e17b5ed feat(cloudflare): add support for MX records (#5283)
  • e324da8 chore(deps): bump renovatebot/github-action (#5556)
  • 70efe5b chore(deps): bump the dev-dependencies group with 2 updates (#5555)
  • d30674b chore(codebase): enable linter recvcheck (#5522)
  • Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request
Dependency Name Ignore Conditions
sigs.k8s.io/external-dns [>= 0.17.a, < 0.18]

Dependabot compatibility score

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)

Bumps [sigs.k8s.io/external-dns](https://github.com/kubernetes-sigs/external-dns) from 0.15.1 to 0.18.0.
- [Release notes](https://github.com/kubernetes-sigs/external-dns/releases)
- [Changelog](https://github.com/kubernetes-sigs/external-dns/blob/master/docs/release.md)
- [Commits](kubernetes-sigs/external-dns@v0.15.1...v0.18.0)

---
updated-dependencies:
- dependency-name: sigs.k8s.io/external-dns
  dependency-version: 0.18.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Jun 30, 2025
@rlymbur rlymbur closed this Jul 7, 2025
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 7, 2025

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/go_modules/sigs.k8s.io/external-dns-0.18.0 branch July 7, 2025 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant