Skip to content

[lightspeed-docs-1.0] OLS-895: small content updates #98119

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 27, 2025
Merged

[lightspeed-docs-1.0] OLS-895: small content updates #98119

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion modules/ols-attaching-a-resource-object-to-your-query.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ This procedure explains how to attach a resource object to provide additional co

. Click the {ols-official} icon in the lower-right corner of the screen.

. Click the plus icon in the {ols-official} user interface to attach a resource object.
. Click *Add* in the {ols-official} user interface to attach a resource object.

. Select the resource object to attach to the question.

Expand Down
4 changes: 2 additions & 2 deletions modules/ols-creating-the-credentials-secret-using-web-console.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ The YAML parameter is always `apitoken` regardless of what the LLM provider call
====
+
.Credential secret for LLM provider
[source,yaml, subs="attributes,verbatim"]
[source,yaml,subs="attributes,verbatim"]
----
apiVersion: v1
kind: Secret
Expand Down Expand Up @@ -68,7 +68,7 @@ type: Opaque
<1> The `api_token` must be `base64` encoded when stored in a secret.
+
.Credential secret for {watsonx}
[source,yaml, subs="attributes,verbatim"]
[source,yaml,subs="attributes,verbatim"]
----
apiVersion: v1
data:
Expand Down
2 changes: 1 addition & 1 deletion modules/ols-filtering-and-redacting-information.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ You should test your regular expressions against sample data to confirm that the
+
.Example custom resource file
+
[source,yaml, subs="attributes,verbatim"]
[source,yaml,subs="attributes,verbatim"]
----
spec:
ols:
Expand Down
6 changes: 3 additions & 3 deletions modules/ols-granting-access-to-individual-users.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ This procedure explains how to grant access to an individual user.

.Procedure

. Run the following command at the command line:
* Run the following command at the command line:
+
[source,terminal]
----
Expand All @@ -34,7 +34,7 @@ $ oc adm policy add-cluster-role-to-user lightspeed-operator-query-access <user_
+
The terminal returns the following output:
+
[source,yaml, subs="attributes,verbatim"]
[source,yaml,subs="attributes,verbatim"]
----
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
Expand All @@ -56,5 +56,5 @@ Save the output as a YAML file, and run the following command to grant user acce
+
[source,terminal]
----
$ oc create -f <yaml_filename>
$ oc create -f <filename>
----
6 changes: 3 additions & 3 deletions modules/ols-granting-access-to-user-group.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ This procedure explains how to grant access to a user group. If your cluster has

.Procedure

. Run the following command at the command line:
* Run the following command at the command line:
+
[source,terminal]
----
Expand All @@ -34,7 +34,7 @@ $ oc adm policy add-cluster-role-to-group lightspeed-operator-query-access <grou
+
The terminal returns the following output:
+
[source,yaml, subs="attributes,verbatim"]
[source,yaml,subs="attributes,verbatim"]
----
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
Expand All @@ -56,5 +56,5 @@ Save the output as a YAML file, and run the following command to grant access to
+
[source,terminal]
----
$ oc create -f <yaml_filename>
$ oc create -f <filename>
----