[Release-1.10] chore: update lcore image from 0.5.3 to 0.6.2

[Jdubrick]

Description of the change

• Bumps LCORE image from 0.5.3 to 0.6.2 for RHDH 1.10.4 release as 0.5.x is going EOL

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

https://redhat.atlassian.net/browse/RHIDP-16122

How to test changes / Special notes to the reviewer

Checklist

• For each Chart updated, version bumped in the corresponding Chart.yaml according to Semantic Versioning.
• For each Chart updated, variables are documented in the values.yaml and added to the corresponding README.md. The pre-commit utility can be used to generate the necessary content. Run pre-commit run --all-files to run the hooks and then push any resulting changes. The pre-commit Workflow will enforce this and warn you if needed.
• JSON Schema template updated and re-generated the raw schema via the pre-commit hook.
• Tests pass using the Chart Testing tool and the ct lint command.
• If you updated the orchestrator-infra chart, make sure the versions of the Knative CRDs are aligned with the versions of the CRDs installed by the OpenShift Serverless operators declared in the values.yaml file. See Installing Knative Eventing and Knative Serving CRDs for more details.

[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

Bump Lightspeed Core sidecar image to 0.6.2 in Backstage Helm chart

⚙️ Configuration changes 📝 Documentation 🕐 10-20 Minutes

AI Description

• Bump Backstage chart version to reflect Lightspeed Core sidecar image update.
• Update default Lightspeed Core sidecar image from 0.5.3 to 0.6.2.
• Regenerate schema and docs to keep values, schema, and README consistent.

Diagram

graph TD
  A([Helm install/upgrade]) --> B["Backstage chart"] --> C["Default values (values.yaml/schema)"] --> D["Backstage Deployment"] --> E[("LCORE image: 0.6.2")]
  F["Chart.yaml version"] --> B
  G["README docs"] --> B

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Pin image by digest instead of tag

• ➕ Improves supply-chain integrity and repeatability across environments
• ➕ Avoids surprise changes if a tag is moved
• ➖ Harder for users to read/override compared to semantic tags
• ➖ Requires a process to update digests regularly

2. Expose a dedicated lcoreVersion value and compose image reference

• ➕ Reduces repeated edits when bumping versions (single source of truth)
• ➕ Makes version bump PRs smaller and less error-prone
• ➖ Adds templating/values complexity and migration considerations
• ➖ May reduce flexibility for users needing fully custom image refs

Recommendation: The current approach (updating the default image tag and keeping README/schema/chart version in sync) is appropriate for a straightforward version bump. If supply-chain guarantees are a priority, consider digest pinning in a follow-up; otherwise, the tag-based bump is simplest and matches typical Helm chart expectations.

Files changed (4) +6 / -6

Documentation (1) +3 / -3

README.mdUpdate README version references and LCORE image default +3/-3

Update README version references and LCORE image default

• Updates the version badge and install command to 5.12.10. Also updates the documented default Lightspeed Core sidecar image reference to 0.6.2.

charts/backstage/README.md

Other (3) +3 / -3

Chart.yamlBump chart patch version to 5.12.10 +1/-1

Bump chart patch version to 5.12.10

• Increments the Backstage Helm chart version from 5.12.9 to 5.12.10 to reflect the updated default sidecar image.

charts/backstage/Chart.yaml

values.schema.jsonUpdate schema default Lightspeed Core sidecar image to 0.6.2 +1/-1

Update schema default Lightspeed Core sidecar image to 0.6.2

• Changes the JSON schema default for the Lightspeed Core sidecar image from 0.5.3 to 0.6.2 to match the chart defaults.

charts/backstage/values.schema.json

values.yamlBump Lightspeed Core sidecar image to 0.6.2 +1/-1

Bump Lightspeed Core sidecar image to 0.6.2

• Updates the chart's default 'global.lightspeed.sidecar.image' to 'quay.io/lightspeed-core/lightspeed-stack:0.6.2'.

charts/backstage/values.yaml

[rhdh-qodo-merge]

Code Review by Qodo

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

1. Lightspeed version skew 🐞 Bug ☼ Reliability

Description

The PR bumps global.lightspeed.sidecar.image to lightspeed-stack:0.6.2 while the chart still
bundles a Lightspeed config branded developer-lightspeed-lls-0.5.x and a RAG bootstrap
initContainer image tagged ...-lls-0.5.0-..., making the default Lightspeed stack internally
inconsistent. The sidecar loads that bundled /app-root/config.yaml at runtime, so the chart now
ships a mixed 0.6.x/0.5.x Lightspeed configuration set by default.

Code

charts/backstage/values.yaml[164]

+      image: quay.io/lightspeed-core/lightspeed-stack:0.6.2

Relevance

●●● Strong

Lightspeed-related chart correctness issues are commonly fixed; mixed 0.6.x/0.5.x defaults risk
broken deployments.

PR-#382

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The sidecar image default was updated to 0.6.2, but the chart still pins the RAG init container to
an lls-0.5.0 image and ships a bundled Lightspeed config branded lls-0.5.x. The Lightspeed stack
config explicitly points the sidecar to load /app-root/config.yaml, and the Helm deployment
template mounts the configured configMaps into the sidecar, so this bundled (0.5.x-branded) config
is what the (0.6.2) sidecar will consume by default.

charts/backstage/values.yaml[126-166]
charts/backstage/files/lightspeed/config.yaml[16-18]
charts/backstage/files/lightspeed/lightspeed-stack.yaml[24-27]
charts/backstage/values.yaml[83-105]
charts/backstage/vendor/backstage/charts/backstage/templates/backstage-deployment.yaml[259-299]

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 chart now defaults the Lightspeed Core sidecar image to `0.6.2`, but it still ships a Lightspeed config and RAG bootstrap init image that are explicitly labeled for `lls-0.5.x` / `lls-0.5.0`. This creates a mixed-version default deployment for Lightspeed.

### Issue Context
The sidecar mounts the bundled Lightspeed configMap files (including `/app-root/config.yaml`) and the Lightspeed stack config points to that path (`library_client_config_path`). With the sidecar image version changed, the bundled config/init content should be reviewed/updated together so the chart ships a coherent Lightspeed stack by default.

### Fix Focus Areas
- charts/backstage/values.yaml[83-105]
- charts/backstage/values.yaml[126-166]
- charts/backstage/files/lightspeed/config.yaml[16-18]
- charts/backstage/files/lightspeed/lightspeed-stack.yaml[24-27]
- charts/backstage/vendor/backstage/charts/backstage/templates/backstage-deployment.yaml[259-299]

### What to change
- Either:
 - Update the bundled Lightspeed config (`files/lightspeed/config.yaml`, and any other bundled Lightspeed payloads if needed) to the matching 0.6.x configuration, **and** bump the RAG initContainer image to the corresponding 0.6.x-compatible `rag-content` image; or
 - Revert the sidecar default image tag back to the 0.5.x series until the bundled config/init assets are updated.
- Keep README/schema defaults in sync with whatever final versions you choose.

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

---

Context

⚠️ Tickets: not configured — ticket URL found in PR but could not be fetched — check ticket provider credentials

✅ Cross-repo context

  Not relevant to this PR: redhat-developer/rhdh

  Not relevant to this PR: redhat-developer/rhdh-plugins

  Not relevant to this PR: redhat-developer/rhdh-must-gather

Tip of the day

💡 Did you know, you can describe a rule in plain language on the Rules page and Qodo drafts it for you

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗