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
+59-40Lines changed: 59 additions & 40 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,37 +36,40 @@ You must manually install and configure the {ls-short} plugin, the {lcs-name} ({
36
36
.. Click *Create ConfigMaps*.
37
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`:
@@ -80,8 +83,24 @@ The {lcs-short} ConfigMap can optionally include configuration for `mcp_servers`
80
83
81
84
.. Click *Create*.
82
85
83
-
. Create the {ls-short} ConfigMap: Create a dedicated {ls-short} ConfigMap (`lightspeed-app-config`) to hold specific plugin configurations.
86
+
. Create an MCP_TOKEN.
87
+
.. https://backstage.io/docs/auth/service-to-service-auth/#static-tokens[Generate the external static token].
88
+
.. Create a secret file as shown in the following example:
89
+
+
90
+
[source,yaml]
91
+
----
92
+
apiVersion: v1
93
+
kind: Secret
94
+
metadata:
95
+
name: lightspeed-secrets
96
+
namespace: <_your_namespace_>
97
+
type: Opaque
98
+
stringData:
99
+
MCP_TOKEN: <_your_static_token>
100
+
----
84
101
102
+
. Create the {ls-short} ConfigMap: Create a dedicated {ls-short} ConfigMap (`lightspeed-app-config`) to hold specific plugin configurations.
103
+
.. Create a
85
104
.. In the {ocp-short} web console, navigate to your {product-very-short} instance and select the *ConfigMaps* tab.
86
105
.. Click *Create ConfigMap*.
87
106
.. From the *Create ConfigMap* page, select the *YAML view* option and add the following example:
@@ -92,7 +111,7 @@ kind: ConfigMap
92
111
apiVersion: v1
93
112
metadata:
94
113
name: lightspeed-app-config
95
-
namespace: <__namespace__> # Enter your {product-very-short} instance namespace
114
+
namespace: <__namespace__> # Enter your RHDH instance namespace
96
115
data:
97
116
app-config.yaml: |-
98
117
backend:
@@ -116,14 +135,14 @@ data:
116
135
# OPTIONAL: Custom users prompts displayed to users
117
136
# If not provided, the plugin uses built-in default prompts
118
137
prompts:
119
-
- title: 'Getting Started with {product}'
138
+
- title: `Getting Started with Red Hat Developer Hub`
120
139
message: Can you guide me through the first steps to start using {product-short} as a developer, like exploring the Software Catalog and adding my service?
121
140
122
141
# OPTIONAL: Port for lightspeed service (default: 8080)
123
142
# servicePort: ${LIGHTSPEED_SERVICE_PORT}
124
143
125
-
# OPTIONAL: Override default {product-very-short} system prompt
126
-
# systemPrompt: "You are a helpful assistant focused on {product} development."
144
+
# OPTIONAL: Override default RHDH system prompt
145
+
# systemPrompt: "You are a helpful assistant focused on Red Hat Developer Hub development."
127
146
----
128
147
129
148
.. Click *Create*.
@@ -165,7 +184,7 @@ where:
165
184
166
185
.. Click *Create*.
167
186
168
-
. Update the dynamic plugins ConfigMap: Add the {ls-short} plugin image to your existing dynamic plugins ConfigMap (`dynamic-plugins-rhdh.yaml`).
187
+
. Update the dynamic plugins ConfigMap: Add the {ls-short} plugin image to your existing dynamic plugins ConfigMap (`dynamic-plugins-rhdh`).
# OPTIONAL: Port for lightspeed service (default: 8080)
202
-
# servicePort: ${LIGHTSPEED_SERVICE_PORT}
203
218
----
204
219
205
220
. Update your deployment configuration: Update the deployment configuration based on how your {product-very-short} instance was installed. You must add two sidecar containers: `llama-stack` and `lightspeed-core`.
@@ -213,7 +228,6 @@ plugins:
213
228
appConfig:
214
229
configMaps:
215
230
- name: lightspeed-app-config
216
-
mountPath: /opt/app-root/src
217
231
----
218
232
... Update the `spec.deployment.patch.spec.template.spec.volumes` specification to include volumes for {lcs-short} configuration (`lightspeed-stack`), shared storage for feedback (`shared-storage`), and RAG data (`rag-data-volume`):
219
233
+
@@ -243,12 +257,17 @@ plugins:
243
257
- mountPath: /data
244
258
name: rag-data-volume
245
259
----
246
-
... Add the Llama Stack and {lcs-short} containers to the `spec.deployment.patch.spec.template.spec.containers` section:
260
+
... Add the Llama Stack, {lcs-short} containers, and the MCP_TOKEN secret file to the `spec.deployment.patch.spec.template.spec.containers` section:
247
261
+
248
262
[source,yaml]
249
263
----
264
+
spec:
265
+
application:
266
+
- extraEnvs:
267
+
secrets:
268
+
- name: lightspeed-secrets
250
269
containers:
251
-
# ... Your existing {product-very-short} container definition ...
0 commit comments