NE-2847: Update external-dns-operator-container-ext-dns-optr-1-3-rhel-9 to bfb278a

[red-hat-konflux-kflux-prd-rh03]

Image created from 'https://github.com/openshift/external-dns-operator?rev=c2af8544f37e0ea3d67ebbe615ee384158ad6424'

This PR contains the following updates:

Package	Update	Change
quay.io/redhat-user-workloads/external-dns-operator-tenant/ext-dns-optr-1-3-rhel-9/external-dns-operator-container-ext-dns-optr-1-3-rhel-9	digest	c3ed5e5 -> bfb278a

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test
This is Konflux nudging PR, not Mintmaker.

[openshift-ci]

Hi @red-hat-konflux-kflux-prd-rh03[bot]. Thanks for your PR.

I'm waiting for a openshift 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.

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.

[grzpiotrowski]

/retitle NE-2847: Update external-dns-operator-container-ext-dns-optr-1-3-rhel-9 to 1fbabeb

[openshift-ci-robot]

@red-hat-konflux-kflux-prd-rh03[bot]: This pull request references NE-2847 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Image created from 'https://github.com/openshift/external-dns-operator?rev=6850ffa3ec876b511fcf82600c9ad1b23961aae4'

This PR contains the following updates:

Package	Update	Change
quay.io/redhat-user-workloads/external-dns-operator-tenant/ext-dns-optr-1-3-rhel-9/external-dns-operator-container-ext-dns-optr-1-3-rhel-9	digest	c3ed5e5 -> 1fbabeb

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test
This is Konflux nudging PR, not Mintmaker.

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]

@red-hat-konflux-kflux-prd-rh03[bot]: 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:

Image created from 'https://github.com/openshift/external-dns-operator?rev=7161b9f84bab17486462ac4cb9ab3fdc3446700b'

This PR contains the following updates:

Package	Update	Change
quay.io/redhat-user-workloads/external-dns-operator-tenant/ext-dns-optr-1-3-rhel-9/external-dns-operator-container-ext-dns-optr-1-3-rhel-9	digest	c3ed5e5 -> 7c05523

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test
This is Konflux nudging PR, not Mintmaker.

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.

[bentito]

/assign @grzpiotrowski

[grzpiotrowski]

/ok-to-test
/lgtm
/approve
/retitle NE-2847: Update external-dns-operator-container-ext-dns-optr-1-3-rhel-9 to bfb278a

[openshift-ci-robot]

@red-hat-konflux-kflux-prd-rh03[bot]: This pull request references NE-2847 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Image created from 'https://github.com/openshift/external-dns-operator?rev=c2af8544f37e0ea3d67ebbe615ee384158ad6424'

This PR contains the following updates:

Package	Update	Change
quay.io/redhat-user-workloads/external-dns-operator-tenant/ext-dns-optr-1-3-rhel-9/external-dns-operator-container-ext-dns-optr-1-3-rhel-9	digest	c3ed5e5 -> bfb278a

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test
This is Konflux nudging PR, not Mintmaker.

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grzpiotrowski

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 [grzpiotrowski]

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

[openshift-ci]

@red-hat-konflux-kflux-prd-rh03[bot]: 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.

[grzpiotrowski]

/retest

I see all integration tests passed in the cluster but here on github they were marked as canceled.

[grzpiotrowski]

/test "Red Hat Konflux kflux-prd-rh03 / Konflux kflux-prd-rh03 / external-dns-fbc-container-ext-dns-optr-fbc-v4-17-on-pull-request"

[grzpiotrowski]

/test "Konflux kflux-prd-rh03 / external-dns-fbc-container-ext-dns-optr-fbc-v4-17-on-pull-request"

[grzpiotrowski]

/retest