chore(intelligent-assistant): 2.1 prerelease changes v1

[michael-valdron]

Target branch

• dev: all development work (features, docs, dependency updates, etc.)

Maybe 2.1 release branch if this does not make the release branch cut.

• release-2.1: bug fixes for a specific supported release

• I have verified this PR targets the correct branch (see branching strategy)

Description

Changes contain the following for 2.1 pre-release:

• Changes image tag reference in compose.yaml and documentation to use 0.7.0rc3 (same as latest_release, should be updated once 0.7.0 is out)
• Removed default OLLAMA_URL environment variable and Ollama related documentation (not supported in 2.1)
• Sync latest lightspeed config changes

Which issue(s) does this PR fix or relate to

• Fixes #issue_number

PR acceptance criteria

• Tests updated and passing
• Documentation updated
• Built-in TechDocs updated if needed. Note that TechDocs changes may need to be reviewed by a Product Manager and/or Architect to ensure content accuracy, clarity, and alignment with user needs.

How to test changes / Special notes to the reviewer

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rhdh-qodo-merge]

PR Summary by Qodo

Prepare Intelligent Assistant configuration for RHDH 2.1

✨ Enhancement 📝 Documentation ⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Pins Lightspeed Core to the 0.7.0rc3 prerelease image.
• Enables synced OKP-backed retrieval for Developer Hub content.
• Removes unsupported Ollama configuration and documentation from the 2.1 experience.

Diagram

graph TD
  USER["Assistant User"] --> RHDH["Developer Hub"] --> CORE["Lightspeed Core 0.7.0rc3"] --> LLM["Supported LLM"]
  CORE --> OKP[("OKP RAG")]

Loading

High-Level Assessment

The current approach is appropriate for a prerelease alignment change: pin the intended image, consume the synced upstream RAG configuration, and remove unsupported Ollama guidance consistently. Retaining Ollama with a warning or using a floating image tag would create misleading support expectations or reduce reproducibility; generic OpenAI-compatible endpoints remain available through the vLLM provider.

Files changed (6) +21 / -61

Documentation (3) +10 / -39

developer-intelligent-assistant.mdRemove Ollama from supported provider examples +2/-2

Remove Ollama from supported provider examples

• Updates setup and data-privacy guidance to list only OpenAI and vLLM as representative supported providers.

docs/getting-started-rhdh/developer-intelligent-assistant.md

maintaining-intelligent-assistant.mdDocument the 0.7.0rc3 default image +2/-2

Document the 0.7.0rc3 default image

• Updates maintainer guidance and the image override example to use Lightspeed Core 0.7.0rc3.

docs/intelligent-assistant/maintaining-intelligent-assistant.md

working-with-intelligent-assistant.mdAlign provider guidance with 2.1 support +6/-35

Align provider guidance with 2.1 support

• Removes the Ollama setup option, environment variables, and troubleshooting references. Renumbers Vertex AI as Option C and updates examples to show the 0.7.0rc3 container image.

docs/intelligent-assistant/working-with-intelligent-assistant.md

Other (3) +11 / -22

compose.yamlPin Lightspeed Core to 0.7.0rc3 +2/-2

Pin Lightspeed Core to 0.7.0rc3

• Replaces the development build with the 0.7.0rc3 prerelease image as the default for the Lightspeed Core service. Updates the adjacent image reference comment accordingly.

compose.yaml

lightspeed-stack.yamlEnable OKP-backed RAG retrieval +9/-10

Enable OKP-backed RAG retrieval

• Activates the synced OKP RAG configuration in offline mode and filters retrieval to Developer Hub content. Configures the retrieval tool to use OKP as its source.

configs/extra-files/lightspeed-stack.yaml

default.envRemove the unsupported Ollama environment setting +0/-10

Remove the unsupported Ollama environment setting

• Removes the OLLAMA_URL template and its container-networking guidance because Ollama is not supported for the 2.1 release.

default.env

[rhdh-qodo-merge]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Image override changes nothing 🐞 Bug ⚙ Maintainability

Description

The override example sets LIGHTSPEED_CORE_IMAGE to the same 0.7.0rc3 image already used by
default. Users following it under the stated condition of selecting a different or custom build
receive no override at all.

Code

docs/intelligent-assistant/maintaining-intelligent-assistant.md[87]

+LIGHTSPEED_CORE_IMAGE=quay.io/lightspeed-core/lightspeed-stack:0.7.0rc3

Relevance

●●● Strong

Accepted precedent supports using a distinct non-default image in override documentation.

PR-#149

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

Compose already defaults to quay.io/lightspeed-core/lightspeed-stack:0.7.0rc3, while the
maintenance guide now uses that exact value as its example for selecting a different image.

compose.yaml[77-80]
docs/intelligent-assistant/maintaining-intelligent-assistant.md[82-88]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The documented `LIGHTSPEED_CORE_IMAGE` override repeats the default image, so copying it does not demonstrate or apply a different image.

## Fix Focus Areas
- docs/intelligent-assistant/maintaining-intelligent-assistant.md[82-88]
- compose.yaml[77-80]

## Recommended Fix
Change the environment-variable example to a clearly distinct custom image or placeholder tag, while retaining `0.7.0rc3` as the documented default.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Context sources

✅ Cross-repo context — repo relationships

  Explored: repo: redhat-developer/rhdh-plugins (sha: ddbeedbd)

Review mode: ⚖️ Balanced: This changes runtime compose image/configuration and enables RAG behavior across multiple files, creating meaningful integration and compatibility risk beyond a lightweight documentation update.

Tip of the day

💡 Did you know, you can route each action level your way: inline, summary, both, or drop

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[rhdh-qodo-merge]

Important

The /generate_labels command by Qodo is sunsetting on the 1st of October 2026 and will no longer be available. We recommend switching to the latest Qodo review capabilities. Learn more

[michael-valdron]

#310 now covers these changes.