Skip to content

OCPBUGS-61213: [OTE] Update webhook ote tests to use latest webhook-operator - #462

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
perdasilva:update-webhook-tests
Sep 10, 2025
Merged

OCPBUGS-61213: [OTE] Update webhook ote tests to use latest webhook-operator#462
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
perdasilva:update-webhook-tests

Conversation

@perdasilva

Copy link
Copy Markdown
Contributor

Due to kube-rbac-proxy deprecation the webhook-operator (created 5 years ago) started to create problems downstream [link].

As a mitigation I've recreated the webhook-operator using a latest version of kubebuilder here. We should definitely eventually move to an in-tree test-operator.

@openshift-ci-robotopenshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 4, 2025
@openshift-ci-robot

Copy link
Copy Markdown

@perdasilva: This pull request references Jira Issue OCPBUGS-61213, which is invalid:

  • expected the bug to target the "4.21.0" version, but no target version was set

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:

Due to kube-rbac-proxy deprecation the webhook-operator (created 5 years ago) started to create problems downstream [link].

As a mitigation I've recreated the webhook-operator using a latest version of kubebuilder here. We should definitely eventually move to an in-tree test-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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ciopenshift-ciBot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 4, 2025
@perdasilva
perdasilvaforce-pushed the update-webhook-tests branch 3 times, most recently from fd1788c to 3c7749aCompareSeptember 4, 2025 15:35
@perdasilva

Copy link
Copy Markdown
ContributorAuthor

/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial 10

@perdasilvaperdasilva changed the title OCPBUGS-61213: Update webhook ote tests to use latest webhook-operatorOCPBUGS-61213: [OTE] Update webhook ote tests to use latest webhook-operatorSep 4, 2025
…rator
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
@openshift-ci

Copy link
Copy Markdown
Contributor

@perdasilva: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e980f570-89a4-11f0-862d-85971cf843d5-0

@perdasilva

Copy link
Copy Markdown
ContributorAuthor

/jire refresh

@perdasilva

Copy link
Copy Markdown
ContributorAuthor

/jira refresh

@openshift-ci-robotopenshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 4, 2025
@openshift-ci-robot

Copy link
Copy Markdown

@perdasilva: This pull request references Jira Issue OCPBUGS-61213, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (bandrade@redhat.com), skipping review request.

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

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.

@anik120anik120 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ciopenshift-ciBot added the lgtm Indicates that a PR is ready to be merged. label Sep 4, 2025
@openshift-ci

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anik120, perdasilva

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:

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

@perdasilva

Copy link
Copy Markdown
ContributorAuthor

/retest

@perdasilva

Copy link
Copy Markdown
ContributorAuthor

/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial 1

@openshift-ci

Copy link
Copy Markdown
Contributor

@perdasilva: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c65e8c70-8a2a-11f0-933c-60756fda7f63-0

@perdasilva

Copy link
Copy Markdown
ContributorAuthor

/retest

2 similar comments
@perdasilva

Copy link
Copy Markdown
ContributorAuthor

/retest

@perdasilva

Copy link
Copy Markdown
ContributorAuthor

/retest

@perdasilva

Copy link
Copy Markdown
ContributorAuthor

/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial 10

@openshift-ci

Copy link
Copy Markdown
Contributor

@perdasilva: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/94442de0-8ae7-11f0-8a60-43dab3307b95-0

@jianzhangbjz

Copy link
Copy Markdown
Contributor

Hi @bandrade, could you help verify it? Thanks!
/assign @bandrade

@tmshort

Copy link
Copy Markdown
Contributor

To not break the bumper
/label tide/merge-method-rebase

@openshift-ciopenshift-ciBot added the tide/merge-method-rebase Denotes a PR that should be rebased by tide when it merges. label Sep 9, 2025
@bandrade

Copy link
Copy Markdown
Contributor

/verified by @bandrade
/label qe-approved

@openshift-ciopenshift-ciBot added the qe-approved Signifies that QE has signed off on this PR label Sep 9, 2025
@openshift-ci-robotopenshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 9, 2025
@openshift-ci-robot

Copy link
Copy Markdown

@bandrade: This PR has been marked as verified by @bandrade.

Details

In response to this:

/verified by @bandrade
/label qe-approved

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

Copy link
Copy Markdown

@perdasilva: This pull request references Jira Issue OCPBUGS-61213, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (bandrade@redhat.com), skipping review request.

Details

In response to this:

Due to kube-rbac-proxy deprecation the webhook-operator (created 5 years ago) started to create problems downstream [link].

As a mitigation I've recreated the webhook-operator using a latest version of kubebuilder here. We should definitely eventually move to an in-tree test-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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 40dae8e and 2 for PR HEAD 3a756aa in total

@tmshort

Copy link
Copy Markdown
Contributor

/retest-required

@tmshort

Copy link
Copy Markdown
Contributor

/test openshift-e2e-aws

@bandrade

Copy link
Copy Markdown
Contributor

/retest

@tmshort

Copy link
Copy Markdown
Contributor

/hold
I want to hold this until after #465, as the automatic bumper jobs aren't working, and this will mess up that manual sync.

@openshift-ciopenshift-ciBot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 10, 2025
@tmshort

Copy link
Copy Markdown
Contributor

/unhold

@openshift-ciopenshift-ciBot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 10, 2025
@openshift-ci

Copy link
Copy Markdown
Contributor

@perdasilva: 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.

@openshift-merge-bot
openshift-merge-botBot merged commit 4f4b107 into openshift:mainSep 10, 2025
13 checks passed
@openshift-ci-robot

Copy link
Copy Markdown

@perdasilva: Jira Issue Verification Checks: Jira Issue OCPBUGS-61213
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-61213 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Due to kube-rbac-proxy deprecation the webhook-operator (created 5 years ago) started to create problems downstream [link].

As a mitigation I've recreated the webhook-operator using a latest version of kubebuilder here. We should definitely eventually move to an in-tree test-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 openshift-eng/jira-lifecycle-plugin repository.

@perdasilva

Copy link
Copy Markdown
ContributorAuthor

/cherry-pick release-4.20

@openshift-cherrypick-robot

Copy link
Copy Markdown

@perdasilva: new pull request created: #469

Details

In response to this:

/cherry-pick release-4.20

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.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approvedIndicates a PR has been approved by an approver from all required OWNERS files.jira/severity-importantReferenced Jira bug's severity is important for the branch this PR is targeting.jira/valid-bugIndicates that a referenced Jira bug is valid for the branch this PR is targeting.jira/valid-referenceIndicates that this PR references a valid Jira ticket of any type.lgtmIndicates that a PR is ready to be merged.qe-approvedSignifies that QE has signed off on this PRtide/merge-method-rebaseDenotes a PR that should be rebased by tide when it merges.verifiedSignifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@perdasilva@openshift-ci-robot@jianzhangbjz@tmshort@bandrade@openshift-cherrypick-robot@anik120