OCPSTRAT-3618: Update etcd test data for k8s 1.37 release - #31605
Conversation
Signed-off-by: jubittajohn <jujohn@redhat.com>
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
|
@jubittajohn: This pull request references OCPSTRAT-3618 which is a valid jira issue. DetailsIn response to this: 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. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughThe etcd storage-path test now includes Kubernetes 1.37 fixtures for new and modified resources. The fixtures define expected storage paths, GVKs, and resource version lifecycle metadata. ChangesEtcd storage-path coverage
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This updates etcd storage-path expectations for Kubernetes 1.37 resources without changing production behavior. No current merge-blocking risk is identified. 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
Full details: Stable And Deterministic Test NamesExplanation PASS: The pull request changes only etcd storage test data in Full details: Test Structure And QualityExplanation The pull request adds only versioned etcd fixture data in Full details: Microshift Test CompatibilityExplanation PASS — The pull request changes only Full details: Single Node Openshift (Sno) Test CompatibilityExplanation PASS: The pull request changes only Full details: Topology-Aware Scheduling CompatibilityExplanation PASS. The commit changes only Full details: Ote Binary Stdout ContractExplanation PASS. The pull request changes only Full details: Ipv6 And Disconnected Network Test CompatibilityExplanation PASS: The commit changes only versioned etcd storage-data entries in Full details: No-Weak-CryptoExplanation The pull request adds only etcd storage-test fixtures in Full details: Container-PrivilegesExplanation PASS: The pull request changes only Full details: No-Sensitive-Data-In-LogsExplanation PASS. The pull request adds static etcd test fixtures only. It adds no logging calls or log-format changes. The added certificate, public-key, and proof-of-possession values are test cryptographic material with no private key. The names and domains use synthetic values such as ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/payload-job-with-prs periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-ovn-serial-1of2 openshift/kubernetes#2738 |
|
@jubittajohn: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/4535d750-a7bd-11f1-9b6e-0dc5280af704-0 |
|
/pipeline required |
|
Scheduling required tests: |
|
/retest-required |
|
/retest-required |
|
/lgtm |
|
/retest-required |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jacobsee, jubittajohn The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
|
@jubittajohn: This PR has been marked as verified by DetailsIn response to this: 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. |
|
@jubittajohn: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Summary by CodeRabbit