Skip to content

Conversation

@sebrandon1
Copy link
Member

This PR updates OpenShift Container Platform documentation URLs to point to the latest available versions.

Changes

  • Automatically updated OCP documentation links using ocp-doc-checker
  • All documentation URLs now point to current versions

Tool Information

This PR was created automatically by scanning the repository with ocp-doc-checker, which identifies and updates outdated OpenShift documentation links.

Repository: https://github.com/sebrandon1/ocp-doc-checker


Tracking Issue: sebrandon1/ocp-doc-checker#18

This commit updates OpenShift Container Platform documentation URLs
to point to the latest available versions.

Updated by: ocp-doc-checker
More info: https://github.com/sebrandon1/ocp-doc-checker
@coderabbitai
Copy link

coderabbitai bot commented Oct 16, 2025

Walkthrough

Two documentation links in docs/operand_metrics.md were updated to reference OpenShift Container Platform 4.20 instead of 4.18; changes occur in the "Enable User Workload Monitoring" and "Query Metrics" sections. No code or exported entities were modified.

Changes

Cohort / File(s) Summary
Documentation version updates
docs/operand_metrics.md
Updated OpenShift Container Platform documentation links from version 4.18 to 4.20 in two sections: "Enable User Workload Monitoring" (ConfigMap doc) and "Query Metrics" (Accessing metrics doc).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check name Status Explanation
Title Check ✅ Passed The pull request title "Update OCP documentation links to latest versions" directly relates to the main change in the changeset. The raw summary confirms that documentation links were updated within the operand_metrics.md file, and the pr_objectives indicate that the links were updated to reference the latest available versions (specifically using the "latest" path after community discussion). The title is concise, specific, and clearly communicates the primary purpose of the changes without being vague or overly broad.
Description Check ✅ Passed The pull request description is clearly related to the changeset and provides relevant context about the updates. It explicitly states that OCP documentation URLs were updated to point to the latest available versions, mentions the automated tool used (ocp-doc-checker), and references the tracking issue. The description is sufficiently specific and not vague, as it explains both what was changed and how the changes were made, making it easy for reviewers to understand the purpose and scope of the PR.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between 25b7fa2 and bff49cd.

📒 Files selected for processing (1)
  • docs/operand_metrics.md (2 hunks)

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 and usage tips.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 16, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sebrandon1
Once this PR has been reviewed and has the lgtm label, please assign lunarwhite 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:

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

### Enable User Workload Monitoring

Cluster administrators can enable monitoring for user-defined projects by setting the `enableUserWorkload: true` field in the cluster monitoring ConfigMap object. For more details, Please look at the detailed documentation to [Configuring user workload monitoring](https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/monitoring/configuring-user-workload-monitoring).
Cluster administrators can enable monitoring for user-defined projects by setting the `enableUserWorkload: true` field in the cluster monitoring ConfigMap object. For more details, Please look at the detailed documentation to [Configuring user workload monitoring](https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/monitoring/configuring-user-workload-monitoring).
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Cluster administrators can enable monitoring for user-defined projects by setting the `enableUserWorkload: true` field in the cluster monitoring ConfigMap object. For more details, Please look at the detailed documentation to [Configuring user workload monitoring](https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/monitoring/configuring-user-workload-monitoring).
Cluster administrators can enable monitoring for user-defined projects by setting the `enableUserWorkload: true` field in the cluster monitoring ConfigMap object. For more details, Please look at the detailed documentation to [Configuring user workload monitoring](https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/monitoring/configuring-user-workload-monitoring).

### Query Metrics

As a cluster administrator or as a user with view permissions for all projects, You can access these metrics using the command line or via the OpenShift web console. For more details, Please look at the detailed documentation to [Accessing metrics](https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/monitoring/accessing-metrics).
As a cluster administrator or as a user with view permissions for all projects, You can access these metrics using the command line or via the OpenShift web console. For more details, Please look at the detailed documentation to [Accessing metrics](https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/monitoring/accessing-metrics).
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
As a cluster administrator or as a user with view permissions for all projects, You can access these metrics using the command line or via the OpenShift web console. For more details, Please look at the detailed documentation to [Accessing metrics](https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/monitoring/accessing-metrics).
As a cluster administrator or as a user with view permissions for all projects, You can access these metrics using the command line or via the OpenShift web console. For more details, Please look at the detailed documentation to [Accessing metrics](https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/monitoring/accessing-metrics).

@sebrandon1
Copy link
Member Author

@bharath-b-rh Would you rather them be latest instead of pointing to a certain release? I can change it if so.

@bharath-b-rh
Copy link
Contributor

@bharath-b-rh Would you rather them be latest instead of pointing to a certain release? I can change it if so.

I feel so, since cert-manager releases aren't directly mapped to OCP releases. The latest always gets translated to the current release, and we wouldn't need to update it after every OCP release.

This commit updates OpenShift Container Platform documentation URLs
to point to the latest available versions.

Updated by: ocp-doc-checker
More info: https://github.com/sebrandon1/ocp-doc-checker
@sebrandon1
Copy link
Member Author

Updated with latest OCP documentation links (ran ocp-doc-checker again).

All documentation URLs now point to the latest available versions.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2025

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

Copy link
Member

@lunarwhite lunarwhite left a comment

Choose a reason for hiding this comment

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

@sebrandon1 first off thanks for your PR!

I assume we don't really need to worry about a version is not "latest" in this markdown doc. The equivalent content for customers reference is already there at https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/security_and_compliance/cert-manager-operator-for-red-hat-openshift#cert-manager-monitoring

My major concern is sometimes the RH docs paths would change between major releases. That means https://docs.redhat.com/.../<a future version>/html/monitoring/configuring-user-workload-monitoring might not always work. But what we could confirm is that 4.18 is not broken and won't be broken in the future.

I'd lean towards we keep it as-is to avoid bumping it every release and verifying if it's still valid. WDYT?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants