Skip to content

CNTRLPLANE-3291: docs: add upstream documentation for configurable log levels - #9193

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
vsolanki12:docs/OCPSTRAT-3156-configurable-log-levels
Aug 7, 2026
Merged

CNTRLPLANE-3291: docs: add upstream documentation for configurable log levels#9193
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
vsolanki12:docs/OCPSTRAT-3156-configurable-log-levels

Conversation

@vsolanki12

@vsolanki12 vsolanki12 commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

Adds upstream documentation for the configurable log levels feature (CNTRLPLANE-3291) at hypershift.pages.dev under "Configure OCP components".

The doc covers:

  • Supported components (KAS, KCM, Scheduler, Etcd, OAPI, OCM, OAuthAPI, OAuth)
  • Log level mappings (Normal/Debug/Trace/TraceAll to klog --v and etcd levels)
  • oc patch examples for setting, checking, and resetting log levels
  • HA guarantees during rolling restart
  • KAS annotation deprecation
  • API reference YAML snippet
  • Tech Preview warning and HCPUserFacingOperatorLogs feature gate prerequisite

Follows existing gated feature documentation pattern (same as Etcd Snapshot Backup Tech Preview docs).

Which issue(s) this PR fixes:

Fixes CNTRLPLANE-3291

Special notes for your reviewer:

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

Summary by CodeRabbit

  • Documentation
    • Added guidance for configuring log levels for HostedCluster control plane components.
    • Documented supported components, log-level mappings, updates and resets, inspection, rolling restarts, and security considerations.
    • Added the new guide to the documentation navigation.

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

openshift-ci-robot commented Jul 31, 2026

Copy link
Copy Markdown

@vsolanki12: This pull request references OCPSTRAT-3156 which is a valid jira issue.

Details

In response to this:

What this PR does / why we need it:

Adds upstream documentation for the configurable log levels feature (OCPSTRAT-3156) at hypershift.pages.dev under "Configure OCP components".

The doc covers:

  • Supported components (KAS, KCM, Scheduler, Etcd, OAPI, OCM, OAuthAPI, OAuth)
  • Log level mappings (Normal/Debug/Trace/TraceAll to klog --v and etcd levels)
  • oc patch examples for setting, checking, and resetting log levels
  • HA guarantees during rolling restart
  • KAS annotation deprecation
  • API reference YAML snippet
  • Tech Preview warning and HCPUserFacingOperatorLogs feature gate prerequisite

Follows existing gated feature documentation pattern (same as Etcd Snapshot Backup Tech Preview docs).

Which issue(s) this PR fixes:

Fixes OCPSTRAT-3156

Special notes for your reviewer:

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

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 openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 31, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

openshift-ci Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@coderabbitai

coderabbitai Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@vsolanki12, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 25 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: eafd7639-16b1-4142-ad01-440756d5f74d

📥 Commits

Reviewing files that changed from the base of the PR and between d52fc83 and 3c1126e.

⛔ Files ignored due to path filters (1)
  • docs/content/reference/aggregated-docs.md is excluded by !docs/content/reference/aggregated-docs.md
📒 Files selected for processing (2)
  • docs/content/how-to/configure-ocp-components/configurable-log-levels.md
  • docs/mkdocs.yml
📝 Walkthrough

Walkthrough

This change adds documentation for configuring HostedCluster control plane component log levels through spec.operatorConfiguration. It documents prerequisites, supported components, log-level values, configuration and reset commands, rolling-restart behavior, TraceAll warnings, kube-apiserver annotation deprecation, and an API reference example. The new page is also added to the MkDocs navigation.

🚥 Pre-merge checks | ✅ 11
✅ Passed checks (11 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the documentation change and the configurable log levels feature addressed by the pull request.
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 The PR changes only documentation and navigation; no Ginkgo test files, test declarations, or dynamic test titles were added.
Test Structure And Quality ✅ Passed The PR changes only two documentation files (+123 and one navigation entry) and adds no Ginkgo test code, so the test-structure requirements are not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed The diff adds only Markdown documentation and one mkdocs navigation entry; no deployment manifests, operator code, controllers, or scheduling constraints were modified.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The commit changes only one Markdown file and mkdocs.yml; it adds no Ginkgo tests, IPv4 assumptions, or external connectivity requirements.
No-Weak-Crypto ✅ Passed The added Markdown and navigation entry contain no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, crypto implementation, or secret-comparison usage.
Container-Privileges ✅ Passed The PR changes only Markdown documentation and navigation. Added content contains no privileged, host namespace, SYS_ADMIN, root, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs ✅ Passed The PR adds documentation only; scans found no log calls or credential/PII literals. It explicitly warns that TraceAll can expose request bodies, tokens, and secrets.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci openshift-ci Bot added area/documentation Indicates the PR includes changes for documentation and removed do-not-merge/needs-area labels Jul 31, 2026
@github-actions
github-actions Bot temporarily deployed to docs-preview/pr-9193 July 31, 2026 10:03 Inactive
@vsolanki12
vsolanki12 force-pushed the docs/OCPSTRAT-3156-configurable-log-levels branch from 9834775 to 74adfb8 Compare July 31, 2026 10:06
@vsolanki12 vsolanki12 changed the title OCPSTRAT-3156: docs: add upstream documentation for configurable log levels CNTRLPLANE-3291: docs: add upstream documentation for configurable log levels Jul 31, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 31, 2026

Copy link
Copy Markdown

@vsolanki12: This pull request references CNTRLPLANE-3291 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 epic to target the "5.0.0" version, but no target version was set.

Details

In response to this:

What this PR does / why we need it:

Adds upstream documentation for the configurable log levels feature (CNTRLPLANE-3291) at hypershift.pages.dev under "Configure OCP components".

The doc covers:

  • Supported components (KAS, KCM, Scheduler, Etcd, OAPI, OCM, OAuthAPI, OAuth)
  • Log level mappings (Normal/Debug/Trace/TraceAll to klog --v and etcd levels)
  • oc patch examples for setting, checking, and resetting log levels
  • HA guarantees during rolling restart
  • KAS annotation deprecation
  • API reference YAML snippet
  • Tech Preview warning and HCPUserFacingOperatorLogs feature gate prerequisite

Follows existing gated feature documentation pattern (same as Etcd Snapshot Backup Tech Preview docs).

Which issue(s) this PR fixes:

Fixes CNTRLPLANE-3291

Special notes for your reviewer:

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

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 coderabbitai Bot 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.

Actionable comments posted: 5

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/content/how-to/configure-ocp-components/configurable-log-levels.md`:
- Around line 45-46: Update the configurable log-level documentation around the
absent logLevel behavior and KAS annotation handling to clarify that the
component’s built-in default is restored only when neither the API field nor the
deprecated KAS annotation is present. Explicitly instruct users to remove the
annotation as well when resetting kube-apiserver to its default.
- Around line 64-68: Revise the documentation around the `logLevel`
rolling-restart statement to place all prerequisites before any zero-downtime
claim. Add the required rollout strategy, readiness/liveness probes, disruption
budget, scheduling spread or affinity, and supported management-cluster
topology; then qualify the HA guarantee as conditional on those prerequisites
rather than relying on replica counts alone.
- Around line 5-7: Update the Tech Preview warning in the configurable log
levels documentation to remove the unsupported
HCPUserFacingOperatorLogs/TechPreviewNoUpgrade prerequisite and state the actual
supported feature-set requirement. Do not reference feature gates that are not
defined in the repository.
- Around line 25-34: Update the configurable log levels documentation to remove
unsupported operatorConfiguration component examples and references, including
the listed control-plane and OAuth fields. Ensure the component table,
configuration examples, API reference, and reset instructions only use fields
defined under spec.operatorConfiguration, or remove the feature documentation if
no supported API field exists.
- Around line 38-44: Update the configurable log levels documentation to remove
or revise any claim that operatorConfiguration supports
spec.operatorConfiguration.<component>.logLevel for kube-apiserver, etcd, or
other components beyond ClusterVersionOperator, ClusterNetworkOperator, and
IngressOperator. Document only the supported component fields and identify the
kube-apiserver annotation path as deprecated where applicable.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: e8bfcee9-1cbc-47ec-a53c-f10a38e0cc9e

📥 Commits

Reviewing files that changed from the base of the PR and between 60ada1e and 9834775.

📒 Files selected for processing (2)
  • docs/content/how-to/configure-ocp-components/configurable-log-levels.md
  • docs/mkdocs.yml

Comment thread docs/content/how-to/configure-ocp-components/configurable-log-levels.md Outdated
@github-actions
github-actions Bot temporarily deployed to docs-preview/pr-9193 July 31, 2026 10:09 Inactive
@vsolanki12
vsolanki12 force-pushed the docs/OCPSTRAT-3156-configurable-log-levels branch from 74adfb8 to a182379 Compare July 31, 2026 10:13
@github-actions
github-actions Bot temporarily deployed to docs-preview/pr-9193 July 31, 2026 10:15 Inactive

@coderabbitai coderabbitai Bot 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.

Actionable comments posted: 1

🧹 Nitpick comments (1)
docs/content/how-to/configure-ocp-components/configurable-log-levels.md (1)

17-19: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Resolve the reported MD046 warnings.

markdownlint-cli2 reports these fenced blocks because the configured style expects indented code blocks. Convert these blocks to the configured style, or verify that fenced blocks are intentionally allowed and update the shared configuration.

Static analysis reports MD046 for these ranges. Based on learnings, keep the required four-space indentation inside the !!! admonitions.

Also applies to: 54-56, 60-62, 72-74, 80-82, 97-121

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/content/how-to/configure-ocp-components/configurable-log-levels.md`
around lines 17 - 19, Resolve MD046 in configurable-log-levels.md by converting
the reported fenced code blocks to indented code blocks, including every listed
range; preserve four-space indentation for code nested inside !!! admonitions.

Sources: Learnings, Linters/SAST tools

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/content/how-to/configure-ocp-components/configurable-log-levels.md`:
- Line 84: Update the reset guidance in the configurable log levels
documentation to replace “verbosity flag” with component-neutral wording such as
“component-specific log-level setting” or “flag or environment variable,” while
preserving the existing reconciliation and built-in-default behavior.

---

Nitpick comments:
In `@docs/content/how-to/configure-ocp-components/configurable-log-levels.md`:
- Around line 17-19: Resolve MD046 in configurable-log-levels.md by converting
the reported fenced code blocks to indented code blocks, including every listed
range; preserve four-space indentation for code nested inside !!! admonitions.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: 779e1671-31a7-42ba-ba93-d35318abaa32

📥 Commits

Reviewing files that changed from the base of the PR and between 74adfb8 and a182379.

📒 Files selected for processing (2)
  • docs/content/how-to/configure-ocp-components/configurable-log-levels.md
  • docs/mkdocs.yml
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/mkdocs.yml

Comment thread docs/content/how-to/configure-ocp-components/configurable-log-levels.md Outdated
@vsolanki12
vsolanki12 force-pushed the docs/OCPSTRAT-3156-configurable-log-levels branch from a182379 to d52fc83 Compare July 31, 2026 10:18
…ANE-3291)

Add documentation for the configurable log levels feature under
how-to/configure-ocp-components/. Covers supported components, log level
mappings, oc patch examples, reset procedure, KAS annotation deprecation,
and API reference. Includes Tech Preview warning and feature gate
prerequisite per existing gated feature documentation pattern.

Signed-off-by: Vimal Solanki <vsolanki@redhat.com>
@vsolanki12
vsolanki12 force-pushed the docs/OCPSTRAT-3156-configurable-log-levels branch from d52fc83 to 3c1126e Compare July 31, 2026 10:23

@coderabbitai coderabbitai Bot 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.

🧹 Nitpick comments (1)
docs/content/how-to/configure-ocp-components/configurable-log-levels.md (1)

17-19: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Resolve the reported MD046 warnings.

markdownlint-cli2 reports MD046 for these fenced code blocks. Convert them to the configured indented style, or verify that fenced blocks are intended and update the lint configuration.

Based on learnings, keep four-space indentation for MkDocs admonition bodies.

Also applies to: 54-56, 60-62, 74-76, 82-84, 99-123

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/content/how-to/configure-ocp-components/configurable-log-levels.md`
around lines 17 - 19, Resolve the MD046 warnings in the affected code blocks by
converting fenced blocks to the configured indented style, while preserving
four-space indentation for code inside MkDocs admonition bodies. Apply this
consistently to the referenced blocks and avoid changing the commands or
surrounding documentation.

Sources: Learnings, Linters/SAST tools

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@docs/content/how-to/configure-ocp-components/configurable-log-levels.md`:
- Around line 17-19: Resolve the MD046 warnings in the affected code blocks by
converting fenced blocks to the configured indented style, while preserving
four-space indentation for code inside MkDocs admonition bodies. Apply this
consistently to the referenced blocks and avoid changing the commands or
surrounding documentation.

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: c3bc7357-9cc0-48fe-a09c-cac9753d294b

📥 Commits

Reviewing files that changed from the base of the PR and between a182379 and d52fc83.

📒 Files selected for processing (2)
  • docs/content/how-to/configure-ocp-components/configurable-log-levels.md
  • docs/mkdocs.yml
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/mkdocs.yml

@vsolanki12
vsolanki12 marked this pull request as ready for review July 31, 2026 10:36
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 31, 2026
@openshift-ci
openshift-ci Bot requested review from csrwng and sdminonne July 31, 2026 10:36

@celebdor celebdor left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

/lgtm

Thanks for the docs. Maybe the api reference at the end is not needed but I don't mind having it.

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

Copy link
Copy Markdown
Contributor

Pipeline controller notification

No second-stage tests were triggered for this PR.

This can happen when:

  • The changed files don't match any pipeline_run_if_changed patterns
  • All files match pipeline_skip_if_only_changed patterns
  • No pipeline-controlled jobs are defined for the main branch

Use /test ? to see all available tests.

@georgelipceanu georgelipceanu 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.

/verified by @georgelipceanu

Manually verified the functionality of this PR by serving MKDocs locally and by confirming that:

  • The Configurable Log Levels for Control Plane Components (Tech Preview) is listed under Configure OCP components in the sidebar nav group of the How-to guides page, and that this was the last option in this nav group and the page itself was accessible
  • The configurable-log-levels.md page loaded without critical errors and without any rendering mistakes
  • The aggregated-docs.md file has a corresponding section that is identical to the content in confirgurable-log-levels.md

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 31, 2026
@openshift-ci-robot

Copy link
Copy Markdown

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

Details

In response to this:

/verified by @georgelipceanu

Manually verified the functionality of this PR by serving MKDocs locally and by confirming that:

  • The Configurable Log Levels for Control Plane Components (Tech Preview) is listed under Configure OCP components in the sidebar nav group of the How-to guides page, and that this was the last option in this nav group and the page itself was accessible
  • The configurable-log-levels.md page loaded without critical errors and without any rendering mistakes
  • The aggregated-docs.md file has a corresponding section that is identical to the content in confirgurable-log-levels.md

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.

@celebdor celebdor removed the verified Signifies that the PR passed pre-merge verification criteria label Jul 31, 2026
@georgelipceanu

Copy link
Copy Markdown
Contributor

Manually verified the functionality of this PR by serving MKDocs locally and by confirming that:

  • The Configurable Log Levels for Control Plane Components (Tech Preview) is listed under Configure OCP components in the sidebar nav group of the How-to guides page, and that this was the last option in this nav group and the page itself was accessible
  • The configurable-log-levels.md page loaded without critical errors and without any rendering mistakes
  • The aggregated-docs.md file has a corresponding section that is identical to the content in confirgurable-log-levels.md

/verified by @georgelipceanu

Also verified actual steps in docs, covered by #8878 (review) (verification comment here)

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 5, 2026
@openshift-ci-robot

Copy link
Copy Markdown

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

Details

In response to this:

Manually verified the functionality of this PR by serving MKDocs locally and by confirming that:

  • The Configurable Log Levels for Control Plane Components (Tech Preview) is listed under Configure OCP components in the sidebar nav group of the How-to guides page, and that this was the last option in this nav group and the page itself was accessible
  • The configurable-log-levels.md page loaded without critical errors and without any rendering mistakes
  • The aggregated-docs.md file has a corresponding section that is identical to the content in confirgurable-log-levels.md

/verified by @georgelipceanu

Also verified actual steps in docs, covered by #8878 (review) (verification comment here)

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.

@csrwng csrwng added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 7, 2026
@openshift-ci

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: celebdor, vsolanki12

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

@vsolanki12

Copy link
Copy Markdown
Contributor Author

/test ci/prow/unit
/test ci/prow/verify

@vsolanki12

Copy link
Copy Markdown
Contributor Author

/test unit
/test verify

@openshift-ci

openshift-ci Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

@vsolanki12: 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-bot Bot merged commit bc42099 into openshift:main Aug 7, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/documentation Indicates the PR includes changes for documentation jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants