Skip to content

Developer Lightspeed guide enhancement: Improved LLM configuration procedures #350

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

Open
Pkylas007 wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Developer Lightspeed guide enhancement: Improved LLM configuration procedures #350

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0c35e31
Developer Lightspeed guide enhancement: Added LLM configuration detai…
Apr 13, 2026
bddcf47
Made formatting changes
Apr 13, 2026
61a92eb
Changed the title of section 2.6
Apr 13, 2026
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 docs/topics/developer-lightspeed/con_developer-lightspeed-pathways.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ As an Administrator, you must complete the following workflow to enable the LLM

* Create a xref:tackle-llm-secret_getting-started[secret] for your LLM key in the Red Hat {ocp-name} cluster.

* In the xref:tackle-enable-llm-proxy_getting-started[Tackle custom resource (CR)], enable the LLM proxy service, enable the Solution Server if you want Migrators to use the Solution Server mode, and configure the LLM provider and the LLM model.
* In the xref:tackle-enable-llm-proxy_getting-started[Tackle custom resource (CR)], enable the LLM proxy service, enable the Solution Server if you want Migrators to use the Solution Server mode, and configure the LLM provider, the LLM model, and the LLM base URL.

As a Migrator, you can:

Expand Down
24 changes: 21 additions & 3 deletions docs/topics/developer-lightspeed/proc_tackle-enable-llm-proxy.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
:_mod-docs-content-type: PROCEDURE

[id="tackle-enable-llm-proxy_{context}"]
= Enabling LLM proxy in the Tackle custom resource
= Configuring the Tackle custom resource

[role="_abstract"]
To use the LLM proxy service, you must enable the proxy in the Tackle custom resource (CR) and deploy it in the Red Hat {ocp-name} project where you installed the {ProductShortName} Operator.
Expand Down Expand Up @@ -33,7 +33,8 @@ To use the Solution Server, the Administrator must enable it in the Tackle CR al
vi tackle
----

. Enable `kai_llm_proxy_enabled` in the Tackle CR:
. Complete one of the following Tackle configurations:
.. Enable LLM proxy and optionally the Solution Server in the Tackle CR:
+
[source, yaml]
----
Expand All @@ -49,9 +50,26 @@ spec:
kai_llm_provider: <provider-name> #For example, OpenAI.
# optional, pick a suitable model for your provider
kai_llm_model: <model-name>
kai_llm_baseurl: "https://<serving-name>-<data-science-project-name>.apps.mta-ai.example.com/v1"
---
----
.. Enter the LLM configurations in the Tackle CR without the proxy service:
+
[source, yaml]
----
---
kind: Tackle
apiVersion: tackle.konveyor.io/v1alpha1
metadata:
name: mta
namespace: openshift-mta
spec:
kai_llm_provider: <provider-name> #For example, OpenAI.
# optional, pick a suitable model for your provider
kai_llm_model: <model-name>
kai_llm_baseurl: "https://<serving-name>-<data-science-project-name>.apps.mta-ai.example.com/v1"
---
----

. Save the Tackle CR configuration.

. Apply the Tackle CR in the `openshift-mta` project:
Expand Down
Loading