register cluster-node-tuning-operator-test-ext the binary to origin for OTE migration

[liqcui]

register cluster-node-tuning-operator-test-ext the binary to origin for OTE migration

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci-robot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[liqcui]

/cc @jmencak Base on the doc https://docs.google.com/document/d/1cFZj9QdzW8hbHc3H0Nce-2xrJMtpDJrwAse9H7hLiWk/edit?tab=t.0, only need to register binary to origin code repository, please review again, thanks!

[jmencak]

/cc @jmencak Base on the doc https://docs.google.com/document/d/1cFZj9QdzW8hbHc3H0Nce-2xrJMtpDJrwAse9H7hLiWk/edit?tab=t.0, only need to register binary to origin code repository, please review again, thanks!

Thank you @liqcui , should we run some rehearsals so that we can see the test logs OTE was successfully ran?

[liqcui]

/cc @jmencak Base on the doc https://docs.google.com/document/d/1cFZj9QdzW8hbHc3H0Nce-2xrJMtpDJrwAse9H7hLiWk/edit?tab=t.0, only need to register binary to origin code repository, please review again, thanks!

Thank you @liqcui , should we run some rehearsals so that we can see the test logs OTE was successfully ran?

I will check current ci job, it should be in the current ci job based the doc

built and included in your component's Dockerfile
registered in origin's extension registry. 

Your tests will automatically run in existing CI jobs (e.g. e2e-aw-ovn, e2e-gcp, etc.)    through origin's orchestration.
The ci-operator automatically:
Builds your test image from the Dockerfile
Includes it in the payload under test
Runs your tests via the openshift-tests framework in existing test suites

You DO NOT need to:
Create new CI job configurations in openshift/release (eg. e2e-*-tests-extension jobs)
Write shell scripts to build or invoke your OTE binary
Add custom test steps to build and run your binary

Your tests will run automatically in:
Component repo presubmits (e.g. e2e-aw-ovn, e2e-gcp, etc.) 
Periodic jobs that include your test suite
Any job running openshift-tests with suites that match your tests

[openshift-ci]

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

[jmencak]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jmencak, liqcui
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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