search

openshift / external-dns-operator

The ExternalDNS Operator provides simplified ExternalDNS controller management.
Apache License 2.0
29 stars 34 forks source link

NE-1802: Update the operand image to 0.14.2 #228

Closed alebedev87 closed 2 months ago

alebedev87 commented 2 months ago

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 commented 2 months ago

@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](https://github.com/openshift/external-dns-operator/pull/228): >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](https://github.com/openshift/external-dns/pull/58). > >External-dns repository from quay.io: [link](https://quay.io/repository/external-dns-operator/external-dns?tab=tags)(`latest` tag). Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fexternal-dns-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-ci-robot commented 2 months ago

@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](https://github.com/openshift/external-dns-operator/pull/228): >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](https://github.com/openshift/external-dns/pull/58). > >External-dns repository from quay.io: [link](https://quay.io/repository/external-dns-operator/external-dns?tab=tags) (`latest` tag). Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fexternal-dns-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
alebedev87 commented 2 months ago

/retest

Cluster provisioning problems on Azure.

alebedev87 commented 2 months ago

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 commented 2 months ago

/retest

alebedev87 commented 2 months ago

/retest

alebedev87 commented 2 months ago

/assign @gcs278

alebedev87 commented 2 months ago

/test e2e-azure-infoblox-operator

Cluster installation failure.

gcs278 commented 2 months ago

/approve /lgtm

openshift-ci[bot] commented 2 months ago

[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](https://github.com/openshift/external-dns-operator/blob/main/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 commented 2 months ago

Azure installations are flaky lately.

/retest

alebedev87 commented 2 months ago

/retest

alebedev87 commented 2 months ago

/retest

gcs278 commented 2 months ago

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 commented 2 months ago

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

openshift-ci-robot commented 2 months ago

@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](https://github.com/openshift/external-dns-operator/pull/228): >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](https://github.com/openshift/external-dns/pull/58). > >External-dns repository from quay.io: [link](https://quay.io/repository/external-dns-operator/external-dns?tab=tags) (`latest` tag). Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fexternal-dns-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
melvinjoseph86 commented 2 months ago

/retest

alebedev87 commented 2 months ago

/retest

alebedev87 commented 2 months ago

/label px-apporved

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

openshift-ci[bot] commented 2 months ago

@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 underlabels -> additional_labelsorlabels -> restricted_labelsinplugin.yaml`?

In response to [this](https://github.com/openshift/external-dns-operator/pull/228#issuecomment-2343363324): >/label px-apporved > >No TE needed for this feature, release notes are enough. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
alebedev87 commented 2 months ago

/label px-approved

jmanthei commented 2 months ago

/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 commented 2 months ago

/retest-required

Remaining retests: 0 against base HEAD 178cf49bbd443487b195d3cbb6dd6a9bc9a918cc and 2 for PR HEAD 44aaacdb4296baff3579a422569fd25c200e616e in total

openshift-ci[bot] commented 2 months ago

@alebedev87: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).