add CI periodic job for CEO

[sandeepknd]

added CI periodic job for CEO.

Summary by CodeRabbit

Adds a periodic OpenShift CI job for the openshift/cluster-etcd-operator repository’s main branch. The job builds the operator and test binaries with pinned dependencies and resource settings, publishes the resulting image for release testing, and runs the disruptive GCP end-to-end operator test every 12 hours.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 9061dbc1-ab76-4703-8719-f89f91ed9c5c

📥 Commits

Reviewing files that changed from the base of the PR and between 6b451e6 and 9651eb3.

⛔ Files ignored due to path filters (2)

• ci-operator/jobs/openshift/cluster-etcd-operator/openshift-cluster-etcd-operator-main-periodics.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/openshift/cluster-etcd-operator/openshift-cluster-etcd-operator-main-presubmits.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (1)

• ci-operator/config/openshift/cluster-etcd-operator/openshift-cluster-etcd-operator-main__periodics.yaml

---

Walkthrough

Adds a periodic CI configuration for cluster-etcd-operator, including pinned base images, binary and container builds, release integration, resource requests, a scheduled GCP disruptive E2E test, and generated repository metadata.

Changes

Cluster etcd operator periodic CI

Layer / File(s)	Summary
Build and release configuration ci-operator/config/openshift/cluster-etcd-operator/...	Defines base images, build commands, repository-based build settings, the cluster-etcd-operator output image, 5.0 release integration, and default resource requests.
GCP disruptive periodic test ci-operator/config/openshift/cluster-etcd-operator/...	Adds the e2e-gcp-operator-disruptive test on a 12-hour schedule with GCP cluster, suite, workflow, and ipi-gcp settings, plus generated metadata.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title matches the main change: adding a new CI periodic job for cluster-etcd-operator.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PR only adds CI YAML/job configs; no Ginkgo It/Describe/Context/When test titles were added or modified, so no unstable names were introduced.
Test Structure And Quality	✅ Passed	Only CI config/job YAML changed; no Ginkgo test code was modified, so this check is not applicable.
Microshift Test Compatibility	✅ Passed	PR only adds CI YAML; no new Ginkgo test code or MicroShift-unsupported API usage is introduced.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PASS: The patch only adds CI YAML; no Go/Ginkgo test code was added, so the SNO test-compatibility check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	Only CI job config was added; no manifests, controllers, node selectors, anti-affinity, PDBs, or topology-dependent scheduling changes.
Ote Binary Stdout Contract	✅ Passed	PR only adds ci-operator YAML; no process-level source code or stdout writes changed, so the OTE stdout contract isn’t implicated.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Only ci-operator YAML/job config changed; no new Ginkgo tests or test code were added, so this compatibility check is not applicable.
No-Weak-Crypto	✅ Passed	Changed files are CI YAML only; scans found no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB or custom crypto/comparison code.
Container-Privileges	✅ Passed	The added CI periodic YAML has no privileged/host* settings, SYS_ADMIN, root context, or allowPrivilegeEscalation.
No-Sensitive-Data-In-Logs	✅ Passed	The new CI YAML contains no log statements or echoed secrets/API keys; it only defines build/test job config.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[sandeepknd]

/assign @dusk125

[openshift-merge-bot]

@sandeepknd: pj-rehearse could not automatically process this event because the request waited in queue for longer than 5 minutes. Use /pj-rehearse to trigger rehearsals manually.

[openshift-ci]

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

[sandeepknd]

/pj-rehearse

[openshift-merge-bot]

@sandeepknd: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[dusk125]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dusk125, sandeepknd

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:

• ci-operator/config/openshift/cluster-etcd-operator/OWNERS [dusk125]
• ci-operator/jobs/openshift/cluster-etcd-operator/OWNERS [dusk125]

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