MON-4607: add zoneinfo to NodeExporterCollectorConfig CRD types by midu16 · Pull Request #2948 · openshift/api

midu16 · 2026-07-23T16:25:02Z

Add NodeExporterCollectorZoneinfoConfig with a collectionPolicy-only struct (matching the softirqs pattern) and the Zoneinfo field to NodeExporterCollectorConfig. Regenerated CRDs, deepcopy, and OpenAPI.

openshift-merge-bot · 2026-07-23T16:25:05Z

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: LGTM mode

openshift-ci-robot · 2026-07-23T16:25:06Z

@midu16: This pull request references MON-4607 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 sub-task to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Add NodeExporterCollectorZoneinfoConfig with a collectionPolicy-only struct (matching the softirqs pattern) and the Zoneinfo field to NodeExporterCollectorConfig. Regenerated CRDs, deepcopy, and OpenAPI.

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.

coderabbitai · 2026-07-23T16:25:26Z

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: bc375f84-5f04-4e68-b3b4-be6fba366592

📥 Commits

Reviewing files that changed from the base of the PR and between 18550f1 and 25978bc.

⛔ Files ignored due to path filters (7)

config/v1alpha1/zz_generated.crd-manifests/0000_10_config-operator_01_clustermonitorings.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
config/v1alpha1/zz_generated.deepcopy.go is excluded by !**/zz_generated*
config/v1alpha1/zz_generated.featuregated-crd-manifests/clustermonitorings.config.openshift.io/ClusterMonitoringConfig.yaml is excluded by !**/zz_generated.featuregated-crd-manifests/**
config/v1alpha1/zz_generated.model_name.go is excluded by !**/zz_generated*
config/v1alpha1/zz_generated.swagger_doc_generated.go is excluded by !**/zz_generated*
openapi/generated_openapi/zz_generated.openapi.go is excluded by !openapi/**, !**/zz_generated*
openapi/openapi.json is excluded by !openapi/**

📒 Files selected for processing (2)

config/v1alpha1/types_cluster_monitoring.go
payload-manifests/crds/0000_10_config-operator_01_clustermonitorings.crd.yaml

📝 Walkthrough

Walkthrough

The node-exporter collector configuration API adds a zoneinfo collector with a collectionPolicy setting. The ClusterMonitoring CRD schema exposes this collector and restricts its policy to Collect or DoNotCollect.

Suggested reviewers: everettraven, joelspeed

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the main change by adding zoneinfo support to NodeExporterCollectorConfig CRD types.
Description check	✅ Passed	The description is directly related to the changeset and correctly summarizes the new zoneinfo config and regenerated artifacts.
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	No Ginkgo test titles were added or modified; the only test change is a standard Go test path constant update, with no dynamic names.
Test Structure And Quality	✅ Passed	No Ginkgo tests were added or modified; the only Go test change is a standard unit-test path update, so the checklist is not applicable.
Microshift Test Compatibility	✅ Passed	No new Ginkgo e2e tests were added; the PR only changes schema/CRD/OpenAPI generation files, so MicroShift test compatibility isn’t applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Diff adds API/CRD schema only; the modified test file changes a constant, and no new Ginkgo specs were added.
Topology-Aware Scheduling Compatibility	✅ Passed	PR only adds API/schema fields for BGP VIP and zoneinfo collectors; no pod affinity, nodeSelector, tolerations, replicas, or topology spread logic was added.
Ote Binary Stdout Contract	✅ Passed	PR changes only schema/generated files; no main/TestMain/init or stdout-writing APIs appear in touched Go paths.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No new Ginkgo e2e tests were added; the only changed Go test is a unit test, and the PR is schema/CRD generation only.
No-Weak-Crypto	✅ Passed	Added only schema/CRD structs for zoneinfo; no weak ciphers, custom crypto, or secret/token comparisons were found.
Container-Privileges	✅ Passed	The PR only adds CRD/OpenAPI schema for zoneinfo; no changed manifest sets privileged, hostPID/hostNetwork/hostIPC, allowPrivilegeEscalation, root, or SYS_ADMIN.
No-Sensitive-Data-In-Logs	✅ Passed	Changed files only add schema/CRD fields and comments for zoneinfo; no new logging or sensitive-data emission was introduced.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.12.2)

Error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented
The command is terminated due to an error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented

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

openshift-ci · 2026-07-23T16:25:55Z

Hello @midu16! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

qodo-for-rh-openshift · 2026-07-23T16:26:03Z

PR Summary by Qodo

Add zoneinfo collector config to ClusterMonitoringConfig node-exporter types

✨ Enhancement ⚙️ Configuration changes 🕐 20-40 Minutes

AI Description

• Add a Zoneinfo collector configuration block to NodeExporterCollectorConfig.
• Introduce NodeExporterCollectorZoneinfoConfig with collectionPolicy semantics matching other
 collectors.
• Regenerate CRD manifests, deepcopy methods, and OpenAPI/Swagger artifacts to expose the new field.

Diagram

graph TD
  A["ClusterMonitoringConfig CR"] --> B["NodeExporterCollectorConfig"] --> C["Zoneinfo config"]
  C --> D["CRD manifests"]
  C --> E["Go codegen"] --> F["OpenAPI JSON"]

High-Level Assessment

The approach (dedicated Zoneinfo config struct with collectionPolicy, mirroring existing collector patterns like softirqs) is consistent with the API style, keeps the CRD schema explicit, and fits existing codegen pipelines. A more generic shared collector-config type could reduce duplication, but would be a broader API refactor with higher compatibility risk than warranted for a single new collector.

Files changed (9) +176 / -1

Enhancement (1) +22 / -0

types_cluster_monitoring.goAdd Zoneinfo collector field and config type to node-exporter API +22/-0

Add Zoneinfo collector field and config type to node-exporter API
• Adds a new Zoneinfo field to NodeExporterCollectorConfig with descriptive API docs. Introduces NodeExporterCollectorZoneinfoConfig containing only collectionPolicy, matching the established collector config pattern.
config/v1alpha1/types_cluster_monitoring.go

Documentation (1) +10 / -0

zz_generated.swagger_doc_generated.goAdd Swagger docs for zoneinfo field and Zoneinfo config type +10/-0

Add Swagger docs for zoneinfo field and Zoneinfo config type
• Extends the NodeExporterCollectorConfig SwaggerDoc map with the zoneinfo field description. Adds a SwaggerDoc map/function for NodeExporterCollectorZoneinfoConfig and its collectionPolicy field.
config/v1alpha1/zz_generated.swagger_doc_generated.go

Other (7) +144 / -1

0000_10_config-operator_01_clustermonitorings.crd.yamlExpose zoneinfo under node-exporter collectors in generated CRD schema +23/-0

Expose zoneinfo under node-exporter collectors in generated CRD schema
• Regenerates the ClusterMonitoringConfig CRD manifest to include the zoneinfo property. Adds validation/enum for collectionPolicy and marks it required within the zoneinfo object.
config/v1alpha1/zz_generated.crd-manifests/0000_10_config-operator_01_clustermonitorings.crd.yaml

zz_generated.deepcopy.goRegenerate deepcopy for Zoneinfo config and collector config struct +17/-0

Regenerate deepcopy for Zoneinfo config and collector config struct
• Updates NodeExporterCollectorConfig DeepCopyInto to copy the new Zoneinfo field. Adds autogenerated DeepCopy/DeepCopyInto methods for NodeExporterCollectorZoneinfoConfig.
config/v1alpha1/zz_generated.deepcopy.go

ClusterMonitoringConfig.yamlRegenerate feature-gated CRD schema with zoneinfo collector config +23/-0

Regenerate feature-gated CRD schema with zoneinfo collector config
• Updates the feature-gated CRD manifest to include the zoneinfo property and its collectionPolicy enum/required constraint, mirroring the main CRD schema.
config/v1alpha1/zz_generated.featuregated-crd-manifests/clustermonitorings.config.openshift.io/ClusterMonitoringConfig.yaml

zz_generated.model_name.goRegister OpenAPI model name for Zoneinfo config type +5/-0

Register OpenAPI model name for Zoneinfo config type
• Adds OpenAPIModelName() for NodeExporterCollectorZoneinfoConfig so it can be referenced in generated OpenAPI definitions.
config/v1alpha1/zz_generated.model_name.go

zz_generated.openapi.goRegenerate OpenAPI Go definitions to include zoneinfo schema +31/-1

Regenerate OpenAPI Go definitions to include zoneinfo schema

• Registers NodeExporterCollectorZoneinfoConfig in GetOpenAPIDefinitions and adds it as a dependency of NodeExporterCollectorConfig. Introduces the schema generator function for the new type and adds the zoneinfo property to the collector config schema.

openapi/generated_openapi/zz_generated.openapi.go

openapi.jsonRegenerate OpenAPI JSON with zoneinfo property and definition +22/-0

Regenerate OpenAPI JSON with zoneinfo property and definition

• Adds the zoneinfo field to the NodeExporterCollectorConfig definition with a reference to the new type. Introduces the NodeExporterCollectorZoneinfoConfig schema definition requiring collectionPolicy with the Collect/DoNotCollect enum.

openapi/openapi.json

0000_10_config-operator_01_clustermonitorings.crd.yamlUpdate payload CRD manifest to include zoneinfo collector config +23/-0

Update payload CRD manifest to include zoneinfo collector config
• Regenerates the shipped CRD payload manifest to include the zoneinfo property and its validation, keeping payload CRDs aligned with the API type changes.
payload-manifests/crds/0000_10_config-operator_01_clustermonitorings.crd.yaml

qodo-for-rh-openshift · 2026-07-23T16:29:10Z

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 29 rules

✅ Skills: api-review

1. No zoneinfo CRD tests 🐞 Bug ⚙ Maintainability

Description

The CRD validation tests for node-exporter collectors don’t exercise the new
spec.nodeExporterConfig.collectors.zoneinfo field, so regressions in its required/enum validation
(e.g., missing collectionPolicy) could ship without test coverage. This is a
maintainability/regression-risk gap rather than a current schema defect.

Code

config/v1alpha1/types_cluster_monitoring.go[R469-476]

+	// zoneinfo configures the zoneinfo collector, which exposes per-zone memory page counts,
+	// watermarks, and protection thresholds from /proc/zoneinfo.
+	// zoneinfo is optional.
+	// When omitted, this means no opinion and the platform is left to choose a reasonable default,
+	// which is subject to change over time. The current default is disabled.
+	// Enable when you need visibility into kernel memory zone allocation and pressure.
+	// +optional
+	Zoneinfo NodeExporterCollectorZoneinfoConfig `json:"zoneinfo,omitempty,omitzero"`

Relevance

⭐ Low
Similar requests to add extra v1alpha1 CRD integration test cases were rejected previously in this
repo.
PR-#2855

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The API adds the new collectors.zoneinfo field, but the existing collector test case enumerates
several collectors without including zoneinfo, so it won’t catch schema regressions specific to
that field.
config/v1alpha1/types_cluster_monitoring.go[461-476]
config/v1alpha1/tests/clustermonitorings.config.openshift.io/ClusterMonitoringConfig.yaml[1976-2024]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The collector validation tests cover several existing collectors but do not include the newly added `collectors.zoneinfo` field. This reduces confidence that the new schema (required `collectionPolicy`, enum values) will remain correct over time.

### Issue Context
`Zoneinfo` was added to `NodeExporterCollectorConfig` and a new `NodeExporterCollectorZoneinfoConfig` type was introduced.

### Fix Focus Areas
- config/v1alpha1/tests/clustermonitorings.config.openshift.io/ClusterMonitoringConfig.yaml[1976-2024]
- config/v1alpha1/types_cluster_monitoring.go[461-476]

### What to change
- Extend the existing “Should be able to create NodeExporterConfig with collectors” test to include:
 - `zoneinfo:
     collectionPolicy: Collect`
- Add a negative test to reject `zoneinfo: {}` (missing required `collectionPolicy`).
- (Optional) Add a negative test for an invalid enum value under `zoneinfo.collectionPolicy`.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Add optional nodeExporter.collectors.zoneinfo toggle (disabled by default). Wire --collector.zoneinfo/--no-collector.zoneinfo in updateNodeExporterArgs, extend unit/e2e tests, and add zoneinfo to telemeter collector success matcher. CRD merge (config_merge.go) will be added once openshift/api#2948 merges and the vendor is updated with the NodeExporterCollectorZoneinfoConfig type.

Add optional nodeExporter.collectors.zoneinfo toggle (disabled by default). Wire --collector.zoneinfo/--no-collector.zoneinfo in updateNodeExporterArgs, extend unit/e2e tests, and add zoneinfo to telemeter collector success matcher. Update jsonnet/versions.yaml to match upstream component versions. CRD merge (config_merge.go) will be added once openshift/api#2948 merges and the vendor is updated with the NodeExporterCollectorZoneinfoConfig type.

midu16 · 2026-07-24T06:31:15Z

/test verify-hypershift-integration

qodo-for-rh-openshift · 2026-07-24T06:31:38Z

PR-Agent: could not find a component named verify-hypershift-integration in a supported language in this PR.

midu16 · 2026-07-24T07:01:29Z

/retest-required

midu16 · 2026-07-24T07:31:23Z

@everettraven @JoelSpeed could you help me understand these failures ? As far as i can see, the issues are environmental not PR/code change wise.

Thank you

Add optional nodeExporter.collectors.zoneinfo toggle (disabled by default). Wire --collector.zoneinfo/--no-collector.zoneinfo in updateNodeExporterArgs, extend unit/e2e tests, and add zoneinfo to telemeter collector success matcher. Update jsonnet/versions.yaml to match upstream component versions. CRD merge (config_merge.go) will be added once openshift/api#2948 merges and the vendor is updated with the NodeExporterCollectorZoneinfoConfig type.

JoelSpeed · 2026-07-24T12:03:12Z

The hypershift integration is broken pending a rebase of the HyperShift dependencies to 1.36, nothing to do with your PR presently

midu16 · 2026-07-24T12:04:51Z

@JoelSpeed thank you for your answer, may i get a feedback/review from your side on the PR ?

everettraven · 2026-07-24T14:16:14Z

Just wanted to mention that this has been assigned to @saschagrunert to review. I believe he mentioned that he will take a look at this on Monday.

midu16 · 2026-07-24T14:18:06Z

Just wanted to mention that this has been assigned to @saschagrunert to review. I believe he mentioned that he will take a look at this on Monday.

Thank you @everettraven

simonpasquier

/lgtm

openshift-merge-bot · 2026-07-24T14:30:16Z

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial-1of2
/test e2e-aws-serial-2of2
/test e2e-aws-serial-techpreview-1of2
/test e2e-aws-serial-techpreview-2of2
/test e2e-azure
/test e2e-gcp
/test e2e-upgrade
/test e2e-upgrade-out-of-change
/test minor-e2e-upgrade-minor

midu16 · 2026-07-25T11:19:28Z

/retest-required

openshift-ci · 2026-07-26T12:13:40Z

@midu16: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/minor-e2e-upgrade-minor	`302b80b`	link	true	`/test minor-e2e-upgrade-minor`
ci/prow/e2e-azure	`302b80b`	link	true	`/test e2e-azure`
ci/prow/e2e-gcp	`302b80b`	link	true	`/test e2e-gcp`
ci/prow/verify-hypershift-integration	`25978bc`	link	true	`/test verify-hypershift-integration`
ci/prow/integration	`25978bc`	link	true	`/test integration`

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.

saschagrunert

LGTM, the change seems to comply to the API guidelines and looks correct.

simonpasquier · 2026-07-27T08:45:56Z

/lgtm

openshift-merge-bot · 2026-07-27T08:48:47Z

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial-1of2
/test e2e-aws-serial-2of2
/test e2e-aws-serial-techpreview-1of2
/test e2e-aws-serial-techpreview-2of2
/test e2e-azure
/test e2e-gcp
/test e2e-upgrade
/test e2e-upgrade-out-of-change
/test minor-e2e-upgrade-minor

openshift-ci · 2026-07-27T08:49:22Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

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

JoelSpeed · 2026-07-27T10:45:12Z

+	// watermarks, and protection thresholds from /proc/zoneinfo.
+	// zoneinfo is optional.
+	// When omitted, this means no opinion and the platform is left to choose a reasonable default,
+	// which is subject to change over time. The current default is disabled.


Disabled isn't actually an option here, so I think this godoc is out of date

JoelSpeed · 2026-07-27T10:46:14Z

+	// which is subject to change over time. The current default is disabled.
+	// Enable when you need visibility into kernel memory zone allocation and pressure.
+	// +optional
+	Zoneinfo NodeExporterCollectorZoneinfoConfig `json:"zoneinfo,omitempty,omitzero"`


Nit, omitempty is superfluous

Suggested change

Zoneinfo NodeExporterCollectorZoneinfoConfig `json:"zoneinfo,omitempty,omitzero"`

Zoneinfo NodeExporterCollectorZoneinfoConfig `json:"zoneinfo,omitzero"`

MON-4558: add zoneinfo to NodeExporterCollectorConfig CRD types

302b80b

Add NodeExporterCollectorZoneinfoConfig with a collectionPolicy-only struct (matching the softirqs pattern) and the Zoneinfo field to NodeExporterCollectorConfig. Regenerated CRDs, deepcopy, and OpenAPI.

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 23, 2026

openshift-ci Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jul 23, 2026

openshift-ci Bot requested review from JoelSpeed and everettraven July 23, 2026 16:30

simonpasquier reviewed Jul 24, 2026

View reviewed changes

openshift-ci Bot assigned simonpasquier Jul 24, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 24, 2026

Merge branch 'openshift:master' into node-exporter-collector-zoneinfo

25978bc

openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 26, 2026

coderabbitai Bot mentioned this pull request Jul 26, 2026

MON-4608: add interrupts to NodeExporterCollectorConfig CRD types #2955

Open

saschagrunert approved these changes Jul 27, 2026

View reviewed changes

coderabbitai Bot mentioned this pull request Jul 27, 2026

MON-4616: add support for dmmultipath collector #2956

Open

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 27, 2026

JoelSpeed reviewed Jul 27, 2026

View reviewed changes

	Zoneinfo NodeExporterCollectorZoneinfoConfig `json:"zoneinfo,omitempty,omitzero"`
	Zoneinfo NodeExporterCollectorZoneinfoConfig `json:"zoneinfo,omitzero"`

Uh oh!

Conversation

midu16 commented Jul 23, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 23, 2026

Uh oh!

openshift-ci-robot commented Jul 23, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai Bot commented Jul 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Uh oh!

openshift-ci Bot commented Jul 23, 2026

Uh oh!

qodo-for-rh-openshift Bot commented Jul 23, 2026

PR Summary by Qodo

Uh oh!

qodo-for-rh-openshift Bot commented Jul 23, 2026

Code Review by Qodo

Uh oh!

midu16 commented Jul 24, 2026

Uh oh!

qodo-for-rh-openshift Bot commented Jul 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

midu16 commented Jul 24, 2026

Uh oh!

midu16 commented Jul 24, 2026

Uh oh!

JoelSpeed commented Jul 24, 2026

Uh oh!

midu16 commented Jul 24, 2026

Uh oh!

everettraven commented Jul 24, 2026

Uh oh!

midu16 commented Jul 24, 2026

Uh oh!

simonpasquier left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-merge-bot Bot commented Jul 24, 2026

Uh oh!

midu16 commented Jul 25, 2026

Uh oh!

openshift-ci Bot commented Jul 26, 2026

Uh oh!

saschagrunert left a comment

Choose a reason for hiding this comment

Uh oh!

simonpasquier commented Jul 27, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 27, 2026

Uh oh!

openshift-ci Bot commented Jul 27, 2026

Uh oh!

JoelSpeed Jul 27, 2026

Choose a reason for hiding this comment

Uh oh!

JoelSpeed Jul 27, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

openshift-ci-robot commented Jul 23, 2026 •

edited by openshift-ci Bot

Loading

coderabbitai Bot commented Jul 23, 2026 •

edited

Loading

qodo-for-rh-openshift Bot commented Jul 24, 2026 •

edited

Loading