Skip to content

OSDOCS-19053: Add Helm to list of CLI tools#111230

Open
jseseCCS wants to merge 1 commit intoopenshift:mainfrom
jseseCCS:OSDOCS-19053
Open

OSDOCS-19053: Add Helm to list of CLI tools#111230
jseseCCS wants to merge 1 commit intoopenshift:mainfrom
jseseCCS:OSDOCS-19053

Conversation

@jseseCCS
Copy link
Copy Markdown
Contributor

@jseseCCS jseseCCS commented May 5, 2026

Version(s): 4.22

Issue: https://redhat.atlassian.net/browse/OSDOCS-19053

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 5, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 5, 2026

@jseseCCS: This pull request references OSDOCS-19053 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 story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Version(s): 4.22

Issue: https://redhat.atlassian.net/browse/OSDOCS-19053

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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.

@jseseCCS
Copy link
Copy Markdown
Contributor Author

jseseCCS commented May 5, 2026

@sowmya-sl could you review this?

@openshift-ci openshift-ci Bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 5, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 5, 2026

Hi @jseseCCS. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

* xref:../cli_reference/rosa_cli/rosa-get-started-cli.adoc#rosa-get-started-cli[ROSA CLI (`rosa`)]: Use the `rosa` CLI to create, update, manage, and delete {product-title} clusters and resources.
endif::openshift-rosa,openshift-rosa-hcp[]

* link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/building_applications/working-with-helm-charts[Helm CLI (`helm`)]: Use the `helm` CLI to install and manage Helm charts on {product-title}.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The version should be the latest.
@webbnh Do you think we should add this change going back to older versions?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Agreed: ideally, this link should refer to the version of the docs which match the version of OCP that the customer is running -- I don't know whether that context is available, here -- in its absence, the link should refer to the the "current" or "latest" version of the docs, which (hopefully) will be 4.22 at the beginning of next month.

And, yes, if it's feasible, it would be good if this reference appeared in the documentation for all the supported versions of OCP.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

How far back do we add it? Till which version that is?

@webbnh
Copy link
Copy Markdown

webbnh commented May 5, 2026

/ok-to-test

@openshift-ci openshift-ci Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 5, 2026
Copy link
Copy Markdown

@webbnh webbnh left a comment

Choose a reason for hiding this comment

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

One question.

* xref:../cli_reference/rosa_cli/rosa-get-started-cli.adoc#rosa-get-started-cli[ROSA CLI (`rosa`)]: Use the `rosa` CLI to create, update, manage, and delete {product-title} clusters and resources.
endif::openshift-rosa,openshift-rosa-hcp[]

* link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/building_applications/working-with-helm-charts[Helm CLI (`helm`)]: Use the `helm` CLI to install and manage Helm charts on {product-title}.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Agreed: ideally, this link should refer to the version of the docs which match the version of OCP that the customer is running -- I don't know whether that context is available, here -- in its absence, the link should refer to the the "current" or "latest" version of the docs, which (hopefully) will be 4.22 at the beginning of next month.

And, yes, if it's feasible, it would be good if this reference appeared in the documentation for all the supported versions of OCP.

* xref:../cli_reference/rosa_cli/rosa-get-started-cli.adoc#rosa-get-started-cli[ROSA CLI (`rosa`)]: Use the `rosa` CLI to create, update, manage, and delete {product-title} clusters and resources.
endif::openshift-rosa,openshift-rosa-hcp[]

* link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/building_applications/working-with-helm-charts[Helm CLI (`helm`)]: Use the `helm` CLI to install and manage Helm charts on {product-title}.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Why does this hyperlink use link: instead of xref: like the earlier references do?

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 5, 2026

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

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

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants