feat: 🔀 Sync upstream v0.20.0

[langecode]

What does it do ?

Motivation

More

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

[gemini-code-assist]

Summary of Changes

Hello @langecode, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates the latest upstream changes from version v0.20.0, focusing on enhancing provider capabilities, refining endpoint validation, and improving integration with Kubernetes resources. Key updates include a new 'strictly owned' feature for the CoreDNS provider, improved Gloo proxy source logic with informer-based caching, and more robust SRV record handling. The changes also encompass extensive dependency updates, documentation improvements, and new end-to-end tests to ensure the system's reliability and correctness.

Highlights

• Upstream Synchronization: This pull request synchronizes the project with upstream version v0.20.0, incorporating a wide range of updates and improvements across the codebase.
• CoreDNS Provider Enhancements: The CoreDNS provider now supports a 'strictly owned' mode, allowing records to be separated by owner ID in a single etcd instance, preventing unintended modifications by other ExternalDNS instances. New e2e tests have been added for CoreDNS.
• Gloo Proxy Source Refinement: The Gloo proxy source has been refactored to utilize informers for better caching and event handling. It also gains the ability to derive DNS targets from Ingress resources referenced by Gloo Gateways, enhancing integration with Kubernetes ingress controllers.
• SRV Record Validation & Trailing Dots: Endpoint validation for SRV records has been improved to ensure the target host explicitly ends with a trailing dot, aligning with RFC 2782. This change also extends to other record types like CNAME, MX, and NS in the PowerDNS provider.
• Service Source Node Exclusion: The service source now includes an option to exclude unschedulable nodes when determining targets for NodePort services, providing more control over DNS record generation based on node status.
• Dependency Updates & Documentation Fixes: Numerous Go module dependencies have been updated to their latest versions, and various documentation files have received minor corrections for typos, grammar, and updated examples.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request is a synchronization with upstream version v0.20.0, bringing a substantial set of features, improvements, and fixes. Key enhancements include improved multi-cluster support for the CoreDNS provider with a new --coredns-strictly-owned flag, and the ability for the gloo-proxy source to resolve targets from an Ingress backing a Gateway. The service source can now exclude unschedulable nodes. The codebase sees performance improvements, notably in the gloo-proxy source which now uses informers. There are also numerous documentation updates, including important clarifications on OwnerID migration for multi-cluster environments. The Helm chart is updated with corrected RBAC rules and schema fixes. The addition of end-to-end tests is a significant improvement to the project's testing infrastructure. Overall, this is a comprehensive update that enhances functionality and maintains the project's health.

[coveralls]

Pull Request Test Coverage Report for Build 20259108938

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 242 unchanged lines in 10 files lost coverage.
• Overall coverage decreased (-0.01%) to 78.605%

---

Files with Coverage Reduction	New Missed Lines	%
openshift_route.go	1	79.49%
apis/externaldns/types.go	1	99.71%
cloudflare/cloudflare.go	2	90.71%
plan.go	3	95.85%
endpoint.go	6	90.6%
coredns/coredns.go	31	90.36%
service.go	42	93.37%
gloo_proxy.go	47	74.18%
pdns/pdns.go	54	70.82%
store.go	55	39.95%

Totals
Change from base Build 19478849983:	-0.01%
Covered Lines:	16169
Relevant Lines:	20570

---

💛 - Coveralls