You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/developer-lightspeed/proc-installing-and-configuring-lightspeed.adoc
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,8 @@ This step is necessary as {ls-short} has a new architecture. In the previous rel
23
23
.Prerequisites
24
24
25
25
* You are logged in to your {ocp-short} account.
26
-
* You have an existing {product-very-short} instance installed using either the Operator or the Helm chart.
26
+
* You have an {product-very-short} instance installed using either the Operator or the Helm chart.
27
+
* You have created a {installing-and-viewing-plugins-book-link}##rhdh-installing-rhdh-plugins_title-plugins-rhdh-about[custom dynamic plugins ConfigMap].
27
28
28
29
.Procedure
29
30
@@ -33,7 +34,7 @@ You must manually install and configure the {ls-short} plugin, the {lcs-name} ({
33
34
34
35
.. In the {ocp-short} web console, navigate to your {product-very-short} instance and select the *ConfigMaps* tab.
35
36
.. Click *Create ConfigMaps*.
36
-
.. From the *Create ConfigMap* page, select the *YAML view* option in *Configure via* and edit the file using the following structure. This example demonstrates the configuration for the LCS ConfigMap, typically named `lightspeed-stack`, which connects to the Llama Stack service locally on port `8321`:
37
+
.. From the *Create ConfigMap* page, select the *YAML view* option and edit the file using the following structure. This example demonstrates the configuration for the LCS ConfigMap, typically named `lightspeed-stack`, which connects to the Llama Stack service locally on port `8321`:
37
38
+
38
39
[source,yaml,subs=+attributes]
39
40
----
@@ -83,7 +84,7 @@ The {lcs-short} ConfigMap can optionally include configuration for `mcp_servers`
83
84
84
85
.. In the {ocp-short} web console, navigate to your {product-very-short} instance and select the *ConfigMaps* tab.
85
86
.. Click *Create ConfigMap*.
86
-
.. From the *Create ConfigMap* page, select the *YAML view* option in *Configure via*, and add the following example:
87
+
.. From the *Create ConfigMap* page, select the *YAML view* option and add the following example:
87
88
+
88
89
[source,yaml]
89
90
----
@@ -131,7 +132,7 @@ data:
131
132
132
133
.. In the {ocp-short} web console, go to *Secrets*.
133
134
.. Click *Create* -> *Key/value secret*.
134
-
.. In the *Create key/value secret* page, select the *YAML view* option in *Configure via*, and add the following example:
135
+
.. In the *Create key/value secret* page, select the *YAML view* option and add the following example:
135
136
+
136
137
[source,yaml]
137
138
----
@@ -164,7 +165,7 @@ where:
164
165
165
166
.. Click *Create*.
166
167
167
-
. Update the dynamic plugins ConfigMap: Add the {ls-short} plugin image to your existing dynamic plugins ConfigMap (`dynamic-plugins-{product-very-short}.yaml`).
168
+
. Update the dynamic plugins ConfigMap: Add the {ls-short} plugin image to your existing dynamic plugins ConfigMap (`dynamic-plugins-rhdh.yaml`).
0 commit comments