[main] update LCORE image from 0.5.2 to 0.5.3

[rm3l]

Manual cherry-pick of #474

[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]

Code Review by Qodo

Sorry, something went wrong

We weren't able to complete the code review on our side. Please try again

[rhdh-qodo-merge]

PR Summary by Qodo

Bump Lightspeed Core sidecar image to 0.5.3 and chart version to 6.2.3

⚙️ Configuration changes 📝 Documentation 🕐 Less than 10 minutes

AI Description

• Bump the Backstage chart version from 6.2.2 to 6.2.3.
• Update default Lightspeed Core sidecar image from 0.5.2 to 0.5.3.
• Refresh README examples/badges to reference the new chart and image versions.

Diagram

graph TD
  U["Cluster operator"] --> H["Helm chart: backstage"] --> V["values.yaml / schema"] --> S["Lightspeed sidecar"] --> I[("quay.io image: 0.5.3")]
  H --> CY["Chart.yaml (6.2.3)"]
  H --> R["README.md (docs)"]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Pin the Lightspeed image by digest (sha256) instead of tag

• ➕ Improves reproducibility by avoiding tag retargeting
• ➕ Reduces supply-chain risk by ensuring the exact image is pulled
• ➖ Requires updating digests on every release and documenting the mapping
• ➖ Less readable than a simple semver tag for users

2. Automate image/chart bumps via release workflow (bot/CI)

• ➕ Reduces manual cherry-pick overhead and drift between repos/branches
• ➕ Standardizes version bump + doc update patterns
• ➖ Upfront CI/workflow work and ongoing maintenance
• ➖ May need human gating for downstream validation requirements

Recommendation: The current approach (bump tag + chart version + docs/schema alignment) is appropriate for a patch update and keeps user overrides intact. If reproducibility/supply-chain constraints are a priority, consider a follow-up to optionally support digest pinning (e.g., allowing either tag or digest in the image reference) rather than changing the default immediately.

Files changed (4) +6 / -6

Documentation (1) +3 / -3

README.mdUpdate README badge/examples and default sidecar image reference +3/-3

Update README badge/examples and default sidecar image reference

• Refreshes the chart version badge and install example to 6.2.3. Updates the documented default Lightspeed Core sidecar image to 0.5.3 in the values table.

charts/backstage/README.md

Other (3) +3 / -3

Chart.yamlBump chart version to 6.2.3 +1/-1

Bump chart version to 6.2.3

• Updates the Helm chart version from 6.2.2 to 6.2.3 to reflect the new packaged defaults.

charts/backstage/Chart.yaml

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

Update schema default Lightspeed Core sidecar image to 0.5.3

• Changes the JSON schema default for the Lightspeed Core sidecar image from 0.5.2 to 0.5.3, keeping validation defaults aligned with values.yaml.

charts/backstage/values.schema.json

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

Bump Lightspeed Core sidecar image default to 0.5.3

• Updates the default global Lightspeed Core sidecar image tag from 0.5.2 to 0.5.3 while preserving the same configuration keys and override behavior.

charts/backstage/values.yaml