OCPBUGS-92839: Add external-dns-operator.v1.3.7 prod bundle to all FBC catalogs

[alebedev87]

Summary

• Add the v1.3.7 prod bundle to stable-v1 and stable-v1.3 channels across all OCP version catalogs (v4.12-v4.22)
• Catalogs regenerated with make generate-catalog OCP_VERSION=<version> for each OCP version

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR updates OLM catalog data for external-dns-operator across catalog versions v4.12 through v4.22. It adds v1.2.4 and v1.3.7 channel entries and bundle image references, updates bundle metadata and related images across generated catalogs, refreshes embedded example payloads, and adds deprecation entries in later catalog files.

Possibly related PRs

• openshift/external-dns-operator#501: Updates the same OLM catalog channel and bundle wiring for external-dns-operator version progression to v1.3.7.
• openshift/external-dns-operator#508: Modifies the same catalog template and bundle path for the v1.2.4 replacement chain and bundle additions.
• openshift/external-dns-operator#513: Changes the external-dns-operator release metadata around the same v1.3.7 catalog update.

Suggested reviewers

• davidesalerno
• jcmoraisjr

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PR only updates catalog YAML files; no test files or Ginkgo titles were added or changed, so the check is not applicable.
Test Structure And Quality	✅ Passed	The PR only changes catalog YAMLs; no Ginkgo test files or test code are in scope, so the test-quality check is not applicable.
Microshift Test Compatibility	✅ Passed	Only catalog YAML files changed; no Ginkgo e2e tests or MicroShift-unsupported OpenShift APIs/features were added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Only catalog YAML files were regenerated; no new Ginkgo/e2e tests or SNO-sensitive node assumptions were added.
Topology-Aware Scheduling Compatibility	✅ Passed	Only catalog YAML metadata changed; no deployment manifests, controllers, or scheduling fields/keywords were introduced.
Ote Binary Stdout Contract	✅ Passed	PR only updates catalog YAMLs; no main/TestMain/BeforeSuite or stdout-writing code was touched.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Only catalog YAML files changed; no new Ginkgo e2e tests were added, so IPv4/disconnected-network test compatibility is not applicable.
No-Weak-Crypto	✅ Passed	The PR only updates catalog YAMLs; scans found no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB or custom crypto code, and the files use sha256 image digests only.
Container-Privileges	✅ Passed	Touched catalog YAMLs only update OLM metadata; searches found no privileged/hostPID/hostNetwork/hostIPC, SYS_ADMIN, runAsUser: 0, or allowPrivilegeEscalation: true fields.
No-Sensitive-Data-In-Logs	✅ Passed	Only OLM catalog YAMLs changed; no logging code or concrete secrets/PII appeared in the diff.
Description check	✅ Passed	The description is related to the PR and correctly summarizes the catalog regeneration and v1.3.7 channel updates.
Title check	✅ Passed	The title matches the main change, though it omits the accompanying v1.2.4 catalog updates.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci-robot]

@alebedev87: This pull request references Jira Issue OCPBUGS-92839, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

• Add the v1.3.7 prod bundle to stable-v1 and stable-v1.3 channels across all OCP version catalogs (v4.12-v4.22)
• Catalogs regenerated with make generate-catalog OCP_VERSION=<version> for each OCP version

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 openshift-eng/jira-lifecycle-plugin repository.

[alebedev87]

/jira refresh

[openshift-ci-robot]

@alebedev87: This pull request references Jira Issue OCPBUGS-92839, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@alebedev87: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

Summary

• Add the v1.2.4 prod bundle to stable-v1 and stable-v1.2 channels across all OCP version catalogs (v4.12-v4.22)
• Add the v1.3.7 prod bundle to stable-v1 and stable-v1.3 channels across all OCP version catalogs (v4.12-v4.22)
• Catalogs regenerated with make generate-catalog OCP_VERSION=<version> for each OCP version

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@alebedev87: This pull request references Jira Issue OCPBUGS-92839, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

• Add the v1.2.4 prod bundle to stable-v1 and stable-v1.2 channels across all OCP version catalogs (v4.12-v4.22)
• Add the v1.3.7 prod bundle to stable-v1 and stable-v1.3 channels across all OCP version catalogs (v4.12-v4.22)
• Catalogs regenerated with make generate-catalog OCP_VERSION=<version> for each OCP version

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@alebedev87: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

Summary

• Add the v1.3.7 prod bundle to stable-v1 and stable-v1.3 channels across all OCP version catalogs (v4.12-v4.22)
• Catalogs regenerated with make generate-catalog OCP_VERSION=<version> for each OCP version

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@alebedev87: This pull request references Jira Issue OCPBUGS-92839, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

• Add the v1.3.7 prod bundle to stable-v1 and stable-v1.3 channels across all OCP version catalogs (v4.12-v4.22)
• Catalogs regenerated with make generate-catalog OCP_VERSION=<version> for each OCP version

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 openshift-eng/jira-lifecycle-plugin repository.

[alebedev87]

All deploy pipelines passed.

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alebedev87

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [alebedev87]

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

[alebedev87]

/test e2e-aws-operator

[alebedev87]

/override ci/prow/e2e-aws-shared-vpc-phz-operator

[openshift-ci]

@alebedev87: Overrode contexts on behalf of alebedev87: ci/prow/e2e-aws-shared-vpc-phz-operator

Details

In response to this:

/override ci/prow/e2e-aws-shared-vpc-phz-operator

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.

[openshift-ci]

@alebedev87: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

[melvinjoseph86]

/lgtm

[openshift-ci-robot]

@alebedev87: Jira Issue OCPBUGS-92839: All pull requests linked via external trackers have merged:

• openshift/external-dns#176
• openshift/external-dns-operator#497
• openshift/external-dns#178
• openshift/external-dns-operator#510
• openshift/external-dns-operator#509
• openshift/external-dns#181
• openshift/external-dns-operator#513
• openshift/external-dns-operator#514
• openshift/external-dns#182
• openshift/external-dns-operator#515

Jira Issue OCPBUGS-92839 has been moved to the MODIFIED state.

Details

In response to this:

Summary

• Add the v1.3.7 prod bundle to stable-v1 and stable-v1.3 channels across all OCP version catalogs (v4.12-v4.22)
• Catalogs regenerated with make generate-catalog OCP_VERSION=<version> for each OCP version

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 openshift-eng/jira-lifecycle-plugin repository.