cutting a new release

[venkatamutyala]

it's been a few months since the last release. Could we get a new release/patch cut? Other projects that are dependent on this one can't be upgraded (e.g. bitnami/external-dns) In particular, this has been merged/fixed: #4483 but a release hasn't been cut yet

[thaynes43]

Any workaround to this? I pulled version 7.3.2 of the bitnami/external-dns chart and it got around the error but when I went to add a second DNSEndpoint it started crashing because it saw the first already existed in cloudflare. When I looked up the error someone said it was fixed in a later version, but I can't update past this afaik until this ticket is resolved.

[venkatamutyala]

@mloiseleur @szuecs any chance you folks could look at cutting a release with the latest fixes?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[venkatamutyala]

I believe this is resolved.