Skip to content

OLS-2613:Update OLS docs for MCP header and definition changes#106086

Open
rh-tokeefe wants to merge 1 commit intoopenshift:lightspeed-docs-mainfrom
rh-tokeefe:OLS-2613
Open

OLS-2613:Update OLS docs for MCP header and definition changes#106086
rh-tokeefe wants to merge 1 commit intoopenshift:lightspeed-docs-mainfrom
rh-tokeefe:OLS-2613

Conversation

@rh-tokeefe
Copy link
Contributor

@rh-tokeefe rh-tokeefe commented Feb 5, 2026

Affects:
lightspeed-main
lightspeed-docs-1.0

PR must be CP'd back to the lightspeed-docs-1.0 branch.

Issue:
https://issues.redhat.com/browse/OLS-2613

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 5, 2026

@rh-tokeefe: This pull request references OLS-2613 which is a valid jira issue.

Details

In response to this:

Version(s):

Issue:

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 5, 2026
@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 5, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 5, 2026

@rh-tokeefe: This pull request references OLS-2613 which is a valid jira issue.

Details

In response to this:

Affects:
lightspeed-main
lightspeed-docs-1.0

PR must be CP'd back to the lightspeed-docs-1.0 branch.

Issue:
https://issues.redhat.com/browse/OLS-2613

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.

@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Feb 5, 2026

🤖 Mon Feb 09 19:34:15 - Prow CI generated the docs preview:

https://106086--ocpdocs-pr.netlify.app/openshift-lightspeed/latest/configure/ols-configuring-openshift-lightspeed.html

@rh-tokeefe
Copy link
Contributor Author

/retest

@blublinsky
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 6, 2026
<4> Specifies the time that the MCP server has to respond to a query. If the client does not receive a query within the time specified, the MCP server times out. In this example, the timeout is 30 seconds.
<5> Define MCP headers as an array of structured objects containing the key-value pairs required for server authentication and context.
<6> Specifies the key that the server uses to authorize the credentials.
<7> Specifies the Kubernetes Secret you are referencing.
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
<7> Specifies the Kubernetes Secret you are referencing.
<7> Specifies the Kubernetes Object you are referencing.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 6, 2026
@openshift-ci
Copy link

openshift-ci bot commented Feb 6, 2026

New changes are detected. LGTM label has been removed.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 9, 2026

@rh-tokeefe: This pull request references OLS-2613 which is a valid jira issue.

Details

In response to this:

Affects:
lightspeed-main
lightspeed-docs-1.0

PR must be CP'd back to the lightspeed-docs-1.0 branch.

Issue:
https://issues.redhat.com/browse/OLS-2613

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.

Copy link
Contributor

@gwynnemonahan gwynnemonahan left a comment

Choose a reason for hiding this comment

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

Render issue, otherwise LGTM.

Note: Tim stated that callouts are being addressed separately, so this still follows the numbered method instead of the definition list or bullet list.

<6> Specifies the key that the server uses to authorize the credentials.
<7> Specifies the Kubernetes object you are referencing.
<8> Specifies the name of the Kubernetes Secret object.
<9> Requires 'kubernetes' to be explicitly stated to fetch values from cluster resources.
Copy link
Contributor

Choose a reason for hiding this comment

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

'kubernetes' doesn't render properly in the preview. It also looks like its in italics here.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

@openshift-ci
Copy link

openshift-ci bot commented Feb 9, 2026

@rh-tokeefe: 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.

@gwynnemonahan
Copy link
Contributor

LGTM.

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

6 participants