chore: release chart for v0.18.0

[elafarge]

What does it do ?

Release a Helm chart for v0.18.0, solves: #5574

NOTE that it's my first time contributing to the external DNS project. I read the release process documentation and tried to stick with it as much as I could but may have missed something 😊

Motivation

Would love to upgrade external-dns on our infrastructure but since there are RBAC changes, a Helm chart upgrade will also be needed.

More

• Yes, this PR title follows Conventional Commits
• Yes, I added unit tests
• Yes, I updated end user documentation accordingly

[k8s-ci-robot]

Welcome @elafarge!

It looks like this is your first PR to kubernetes-sigs/external-dns 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/external-dns has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @elafarge. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[mloiseleur]

/assign @stevehipwell

[stevehipwell]

Thanks @elafarge you've done a good job following the docs. I think we're just waiting on #5578 to be merged at which point could you please rebase and update the release date?

[ivankatliarchuk]

/ok-to-test

[stevehipwell]

@elafarge you should be good to rebase now.

[elafarge]

@elafarge you should be good to rebase now.

Just did so :) EDIT: forgot the date update, just force-pushed 5 minutes later to fix that

[stevehipwell]

@elafarge could you please merge the ### Fixed changelog sections (heading order is in the comment above un-released) and couple you please an an entry for your change to update the versions?

[elafarge]

@elafarge could you please merge the ### Fixed changelog sections (heading order is in the comment above un-released) and couple you please an an entry for your change to update the versions?

All taken care of @stevehipwell

[mloiseleur]

/lgtm

[stevehipwell]

Thanks @elafarge.

/label tide/merge-method-squash
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stevehipwell

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• charts/OWNERS [stevehipwell]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment