Skip to content

OpenShift docs for 4.19 are already available#3032

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:masterfrom
celdrake:available-openshift-4.19-docs
Jul 7, 2025
Merged

OpenShift docs for 4.19 are already available#3032
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:masterfrom
celdrake:available-openshift-4.19-docs

Conversation

@celdrake
Copy link
Contributor

@celdrake celdrake commented Jul 4, 2025

Made some changes to doc links since OpenShift 4.19 is now Generally Available:

  1. When users choose OpenShift 4.19, the documentation links are for that version instead of 4.18

  2. Service mesh operator:
    The previous link was for the documentation of Service Mesh 1.x which is now unsupported, plus Service Mesh has now official docs separate from OpenShift docs. I modified the link to the documentation for the standalone docs of Service Mesh 3.x

  3. Local Storage Operator:
    There are no docs in docs.openshift.com for LSO for OpenShift 4.19. Modified to the correct documentation in docs.redhat.com

  4. Nmstate operator: The old docs in docs.openshift.com don't have the equivalent for 4.19. The new link seems to work with quite old OCP versions.

  5. Pipelines and Serverless operators: The versions we linked for these operators were pretty outdated. I updated the links to docs.redhat.com links and to their latest versions.

Summary by CodeRabbit

  • New Features

    • Updated documentation links throughout the application to point to the latest Red Hat documentation, including new versions and revised URL structures for various operators and features.
  • Bug Fixes

    • Simplified and improved the reliability of documentation links for Service Mesh and other operators by removing version-dependent logic and using fixed URLs where appropriate.

@coderabbitai
Copy link

coderabbitai bot commented Jul 4, 2025

"""

Walkthrough

The changes update documentation link constants and functions to use new Red Hat documentation domains, updated versions, and revised URL structures. The Service Mesh operator spec's description logic is simplified by removing the OpenShift version parameter, reflecting the new static documentation link structure.

Changes

File(s) Change Summary
libs/ui-lib/lib/common/components/operators/operatorSpecs.tsx Removed openshiftVersion from the Service Mesh operator's Description props and corresponding link call.
libs/ui-lib/lib/common/config/docs_links.ts Updated documentation URLs to new Red Hat domains and versions; adjusted link logic; replaced getServiceMeshLink with a static constant.

Suggested labels

lgtm, size/S

Suggested reviewers

  • ammont82
  • rawagner

Poem

A hop to new docs, URLs now shine,
With Red Hat links, all crisp and fine.
Service Mesh simplified, no version to fetch,
Operators rejoice—no more complex stretch!
🐇✨

Docs updated, code refined,
Another carrot for the clever mind!
"""

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.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

libs/ui-lib/lib/common/components/operators/operatorSpecs.tsx

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the config "@openshift-assisted/eslint-config" to extend from. Please check that the name of the config is correct.

The config "@openshift-assisted/eslint-config" was referenced from the config file in "/libs/ui-lib/.eslintrc.cjs".

If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.

libs/ui-lib/lib/common/config/docs_links.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the config "@openshift-assisted/eslint-config" to extend from. Please check that the name of the config is correct.

The config "@openshift-assisted/eslint-config" was referenced from the config file in "/libs/ui-lib/.eslintrc.cjs".

If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4fb8af4 and d92a70c.

📒 Files selected for processing (2)
  • libs/ui-lib/lib/common/components/operators/operatorSpecs.tsx (2 hunks)
  • libs/ui-lib/lib/common/config/docs_links.ts (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • libs/ui-lib/lib/common/components/operators/operatorSpecs.tsx
  • libs/ui-lib/lib/common/config/docs_links.ts
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: tests
  • GitHub Check: circular-deps
  • GitHub Check: translation-files
  • GitHub Check: unit-tests
  • GitHub Check: format
  • GitHub Check: lint
✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@openshift-ci openshift-ci bot requested review from batzionb and jgyselov July 4, 2025 13:09
@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 4, 2025
@celdrake
Copy link
Contributor Author

celdrake commented Jul 4, 2025

@ammont82 Do you think it's worth creating a ticket so QE can verify all the links?

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
libs/ui-lib/lib/common/config/docs_links.ts (1)

167-172: Clean up unused variable in the conditional logic.

The function correctly implements version-specific URL logic, but there's a minor code quality issue.

 export const getLsoLink = (ocpVersion?: string) => {
-  const version = getDocsOpenshiftVersion(ocpVersion);
   return isMajorMinorVersionEqualOrGreater(ocpVersion, '4.19')
     ? `https://docs.redhat.com/container-platform/4.19/storage/persistent_storage/persistent_storage_local/ways-to-provision-local-storage.html`
-    : `https://docs.openshift.com/container-platform/${version}/storage/persistent_storage/persistent_storage_local/ways-to-provision-local-storage.html`;
+    : `https://docs.openshift.com/container-platform/${getDocsOpenshiftVersion(ocpVersion)}/storage/persistent_storage/persistent_storage_local/ways-to-provision-local-storage.html`;
 };
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b30cc70 and 4fb8af4.

📒 Files selected for processing (2)
  • libs/ui-lib/lib/common/components/operators/operatorSpecs.tsx (1 hunks)
  • libs/ui-lib/lib/common/config/docs_links.ts (3 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (2)
libs/ui-lib/lib/common/components/operators/operatorSpecs.tsx (2)
libs/ui-lib/lib/common/components/operators/operatorDescriptions.tsx (1)
  • DESCRIPTION_SERVICEMESH (54-55)
libs/ui-lib/lib/common/config/docs_links.ts (1)
  • getServiceMeshLink (194-195)
libs/ui-lib/lib/common/config/docs_links.ts (1)
libs/ui-lib/lib/common/utils.ts (1)
  • isMajorMinorVersionEqualOrGreater (138-143)
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: tests
  • GitHub Check: unit-tests
  • GitHub Check: translation-files
  • GitHub Check: circular-deps
  • GitHub Check: format
  • GitHub Check: lint
🔇 Additional comments (7)
libs/ui-lib/lib/common/config/docs_links.ts (6)

3-3: LGTM! Version constant updated correctly.

The LATEST_OPENSHIFT_DOCS_VERSION constant has been properly updated from '4.18' to '4.19', which aligns with the PR objective.


194-195: LGTM! Service Mesh function correctly simplified.

The function has been appropriately simplified to return a fixed URL for Service Mesh 3.0 documentation, removing the version parameter dependency. This aligns with the changes in the operatorSpecs.tsx file.


180-182: Documentation path confirmed

The Node Feature Discovery operator documentation URL returns HTTP 200, so the updated docs.redhat.com/.../html/.../psap-node-feature-discovery-operator path is correct. Approving these changes.


192-192: Verified: Pipelines operator docs link is correct
Version 1.18 is the latest GA release of the Red Hat OpenShift Pipelines Operator, and the URL at the location below accurately points to its documentation. No changes required.

• File: libs/ui-lib/lib/common/config/docs_links.ts
Line 192 – 'https://docs.redhat.com/en/documentation/red_hat_openshift_pipelines/1.18/html/installing_and_configuring/installing-pipelines';


198-198: Approve: Updated Serverless operator documentation link to v1.36

Version 1.36 is the current Red Hat OpenShift Serverless Operator release (as of July 4, 2025), so the documentation URL is correct and no further changes are needed.


175-177: Verify the fragment identifier in the Networking Operators docs

Our automated check didn’t find the #k8s-nmstate-about-the-k8s-nmstate-operator anchor on the 4.19 Networking Operators page. Please manually confirm that this fragment ID exists (or update it to match the actual heading ID in the docs).

• File: libs/ui-lib/lib/common/config/docs_links.ts
• Lines: 175–177
• URL under test:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/networking/networking-operators#k8s-nmstate-about-the-k8s-nmstate-operator

libs/ui-lib/lib/common/components/operators/operatorSpecs.tsx (1)

288-293: LGTM! Service Mesh component correctly updated.

The changes properly align with the simplified getServiceMeshLink function:

  • Removed the unused openshiftVersion parameter from the component props
  • Updated the function call to not pass any arguments

This maintains consistency with the changes in docs_links.ts and correctly implements the new static documentation link approach for Service Mesh.

@celdrake celdrake force-pushed the available-openshift-4.19-docs branch from 4fb8af4 to a77129e Compare July 4, 2025 13:17
@celdrake celdrake force-pushed the available-openshift-4.19-docs branch from a77129e to d92a70c Compare July 4, 2025 13:28
@ammont82
Copy link
Member

ammont82 commented Jul 7, 2025

@ammont82 Do you think it's worth creating a ticket so QE can verify all the links?

@celdrake yes. We can create a ticket to verify all the links. Add to this PR the ticket number. Thanks!

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2025
@openshift-ci
Copy link

openshift-ci bot commented Jul 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ammont82, celdrake

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

@openshift-merge-bot openshift-merge-bot bot merged commit 485d2e6 into openshift-assisted:master Jul 7, 2025
11 checks passed
ammont82 pushed a commit to ammont82/assisted-installer-ui that referenced this pull request Sep 12, 2025
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. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants