NE-1802: Update the operand image to 0.14.2

[alebedev87]

This PR updates the operand image to include the latest changes from the upstream's 0.14.2 version, as introduced in the rebase PR.

External-dns repository from quay.io: link (latest tag).

[openshift-ci-robot]

@alebedev87: This pull request references NE-1802 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 "4.18.0" version, but no target version was set.

In response to this:

This PR updates the operand image to include the latest changes from the upstream's 0.14.2 version, as introduced in the rebase PR.

External-dns repository from quay.io: link(latest tag).

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 NE-1802 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 "4.18.0" version, but no target version was set.

In response to this:

This PR updates the operand image to include the latest changes from the upstream's 0.14.2 version, as introduced in the rebase PR.

External-dns repository from quay.io: link (latest tag).

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]

/retest

Cluster provisioning problems on Azure.

[alebedev87]

Azure failures are related to a reached limit for CI DNS zone:

message": "You have reached or exceeded the maximum number of record resources in zone 'ci.azure.devcluster.openshift.com'. You have 10000 record resources of 10000 allowed."

[alebedev87]

/retest

[alebedev87]

/retest

[alebedev87]

/assign @gcs278

[alebedev87]

/test e2e-azure-infoblox-operator

Cluster installation failure.

[gcs278]

One nit pick, otherwise LGTM

[gcs278]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gcs278

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [gcs278]

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

[alebedev87]

Azure installations are flaky lately.

/retest

[alebedev87]

/retest

[alebedev87]

/retest

[gcs278]

There's some slack activity on the DNS records filling up which is causing azure installs to fail. It may work now, if it hasn't filled up again.
/test e2e-azure-infoblox-operator

[melvinjoseph86]

Tested the pr using cluster bot, basic functionality is working. Hence approving from QE side.
/label qe-approved

[openshift-ci-robot]

@alebedev87: This pull request references NE-1802 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 "4.18.0" version, but no target version was set.

In response to this:

This PR updates the operand image to include the latest changes from the upstream's 0.14.2 version, as introduced in the rebase PR.

External-dns repository from quay.io: link (latest tag).

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.

[melvinjoseph86]

/retest

[alebedev87]

/retest

[alebedev87]

/label px-apporved

No TE needed for this feature, release notes are enough.

[openshift-ci]

@alebedev87: The label(s) `/label px-apporved

cannot be applied. These labels are supported:acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, staff-eng-approved. Is this label configured under labels -> additional_labelsorlabels -> restricted_labelsinplugin.yaml`?

In response to this:

/label px-apporved

No TE needed for this feature, release notes are enough.

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.

[alebedev87]

/label px-approved

[jmanthei]

/label docs-approved

In the release notes we will mention that we now use 0.14.2 version of the upstream project.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 178cf49 and 2 for PR HEAD 44aaacd in total

[openshift-ci]

@alebedev87: all tests passed!

Full PR test history. Your PR dashboard.

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.