External-DNS Chart Broken with 7.3.3 due to removal of protected CRD group annotation about charts HOT 8 OPEN

Our automation looks for new releases at https://github.com/kubernetes-incubator/external-dns. When a new release is cut there, our automated test & release process is triggered. As part of that process, the upstream CRDs are compared and the ones in the Bitnami chart are updated to match the upstream, i.e 375ee3b

from charts.

Still broken in 7.5.0

from charts.

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

from charts.

@carrodher I wouldn't know where to begin as the original change was made by some form of automation, which tells me that it too would need to be fixed. I also unfortunately need approval from my company before contributing, even to tools we use, and that would likely take more time than others broken by this change would appreciate.

from charts.

I have added the annotation to the pull request on the original external-dns project, I believe this is where the Bitnami automation gets its information from so if this gets approved hopefully the next release will contain it again?

from charts.

This has been fixed now with kubernetes-sigs/external-dns@f46676f

I don't know the next steps though, I suppose a release needs to be done and then the bitnami chart updated to refer to the new release?

from charts.

I think the release of such updates is automated, not sure how they are triggered but I expect that it will come within a reasonable time.

from charts.

external-dns hasn't issued a new release yet so there's nothing for the new chart to go off of

from charts.