Skip to content

feat(lightspeed): re-enable built-in Lightspeed by default - #786

Closed
rhdh-bot wants to merge 2 commits into
mainfrom
RHIDP-18787-re-enable-lightspeed
Closed

rhdh-bot wants to merge 2 commits into
mainfrom
RHIDP-18787-re-enable-lightspeed

Conversation

@rhdh-bot

@rhdh-bot rhdh-bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Collaborator

What

Flips global.lightspeed.enabled back to true in the deprecated charts/backstage chart (values.yaml, values.schema.json default + default-values tree, README, version bump 7.0.99 → 7.0.100) and removes the stale FIXME referencing RHIDP-15458.

Important finding while validating

The new standalone charts/rhdh chart (v3.5.18, RHDHPLAN-1058) already ships intelligentAssistant.enabled: true — the disabled default only exists on the deprecated charts/backstage chart (disable commit 53117c2, Jul 15, "DPDY issues in next catalog index image"). The midstream values patch (intelligentAssistant.core.image → lightspeed-stack-rhel9 digest pinning) targets the new chart structure, so the productized 2.2 chart lineage already enables the Intelligent Assistant. This PR is therefore consistency cleanup on the deprecated chart, not the enablement vehicle.

Why still worth it

  • The stale FIXME points at RHIDP-15458 ("Re-enable Lightspeed in Operator/Helm/Local") which is Closed/Done for 2.1.0 — the Helm part never landed on either chart; the new chart simply superseded it with enabled-by-default.
  • Anyone still installing the deprecated backstage chart gets a consistent default.

Multi-arch verification (RHIDP-18787)

Component Image Verified
LCS stack (sidecar) registry.redhat.io/lightspeed-core/lightspeed-stack-rhel9:0.6.7 manifest list: amd64 + arm64
OKP image registry.redhat.io/offline-knowledge-portal/rhokp-rhel9 manifest list: amd64 + arm64
RAG init container quay.io/redhat-ai-dev/rag-content:release-1.10-lls-0.5.0-8c231a3b… manifest list: amd64 + arm64 (pinned tag)

Notes

  • Draft pending confirmation from the IA team (Jordan Dubrick) that the DPDY catalog-index issue is fully resolved.
  • The ci/with-lightspeed-service-host-values.yaml scenario does not set enabled, so it resumes exercising the enabled path.
  • charts/backstage/ci/with-lightspeed-disabled-values.yaml still explicitly disables for the negative-path CI scenario (unchanged).

Jira: RHIDP-18787, RHIDP-15458

Flip global.lightspeed.enabled back to true (values, schema default,
README) now that the re-enable ticket RHIDP-15458 is closed and the
DPDY catalog-index issue is resolved.

All Intelligent Assistant images verified multi-arch (RHIDP-18787):
- lightspeed-core/lightspeed-stack-rhel9: manifest list amd64+arm64
- offline-knowledge-portal/rhokp-rhel9: manifest list amd64+arm64
- quay.io/redhat-ai-dev/rag-content (init container): manifest list
  amd64+arm64 at the pinned tag

Signed-off-by: Martin Polasko <mpolasko@redhat.com>
- README: trailing period to match helm-docs output
- values.schema.json: flip enabled in the default-values tree to match
  values.yaml (missed occurrence beside the properties entry)
- Chart.yaml: 7.0.99 -> 7.0.100 (ct lint requires a version bump)

Signed-off-by: Martin Polasko <mpolasko@redhat.com>
@sonarqubecloud

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

⚠️ Pre-commit hook failures

The pre-commit hooks detected issues that need to be fixed.

To fix these issues:

  1. Install the required dependencies:

  2. Run pre-commit on all files:

    pre-commit run --all-files
  3. Commit and push any resulting changes

@rhdh-bot

Copy link
Copy Markdown
Collaborator Author

Closing — will be re-opened under the author's own account (the commits on the branch are already authored correctly). Same branch, same changes.

@rhdh-bot rhdh-bot closed this Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants