[Release-1.10] chore: update LCORE image from 0.5.2 to 0.5.3

[Jdubrick]

Description of the change

• Bumps LCORE image to 0.5.3

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

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

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.5.3 in Backstage Helm chart

⚙️ Configuration changes 📝 Documentation 🕐 10-20 Minutes

AI Description

• Bump Backstage chart patch version to publish updated defaults.
• Update default Lightspeed Core sidecar image reference from 0.5.2 to 0.5.3.
• Regenerate schema/docs to keep chart metadata and values documentation consistent.

Diagram

graph TD
  C["charts/backstage/Chart.yaml"] --> H["Backstage Helm chart"] --> P["Backstage pod"] --> I["Lightspeed sidecar (0.5.3)"]
  V["charts/backstage/values.yaml"] --> H
  S["charts/backstage/values.schema.json"] --> H
  D["charts/backstage/README.md"] --> H

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Pin image by digest (immutable reference)

• ➕ Stronger supply-chain/reproducibility guarantees than a mutable tag
• ➕ Avoids unexpected changes if an upstream tag is ever re-pushed
• ➖ Requires digest management and periodic refresh
• ➖ Harder to read and override in values without tooling support

2. Centralize image version in a single chart value (e.g., separate tag field)

• ➕ Reduces repetition across values.yaml, schema, and README generation inputs
• ➕ Makes future bumps less error-prone
• ➖ May not match existing chart conventions (full image reference override)
• ➖ Still requires regeneration of docs/schema outputs

Recommendation: The current approach (bumping the default full image reference + chart patch version and keeping schema/docs in sync) is appropriate for a Helm chart release branch. If reproducibility or supply-chain controls are a priority, consider a follow-up to support digest-pinning (optionally alongside the tag) while preserving the current full-reference override behavior for disconnected environments.

Files changed (4) +6 / -6

Documentation (1) +3 / -3

README.mdUpdate chart version references and Lightspeed sidecar image doc +3/-3

Update chart version references and Lightspeed sidecar image doc

• Updates the README version badge and example install command to 5.12.8. Updates the documented default for 'global.lightspeed.sidecar.image' to use the 0.5.3 image tag.

charts/backstage/README.md

Other (3) +3 / -3

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

Bump chart version to 5.12.8

• Increments the Helm chart version from 5.12.7 to 5.12.8 to reflect the updated packaged defaults.

charts/backstage/Chart.yaml

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

Update schema default for Lightspeed sidecar image to 0.5.3

• Updates the JSON schema default value for the Lightspeed Core sidecar image from 0.5.2 to 0.5.3 to match chart defaults.

charts/backstage/values.schema.json

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

Bump default Lightspeed Core sidecar image to 0.5.3

• Updates 'global.lightspeed.sidecar.image' default from 'quay.io/lightspeed-core/lightspeed-stack:0.5.2' to ':0.5.3'. No other Lightspeed defaults are changed.

charts/backstage/values.yaml

[rhdh-qodo-merge]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

[rm3l]

/cherry-pick main

[openshift-cherrypick-robot]

@rm3l: once the present PR merges, I will cherry-pick it on top of main in a new PR and assign it to you.

Details

In response to this:

/cherry-pick main

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@rm3l: #474 failed to apply on top of branch "main":

Applying: chore: update LCORE image from 0.5.2 to 0.5.3
Using index info to reconstruct a base tree...
M	charts/backstage/Chart.yaml
M	charts/backstage/README.md
M	charts/backstage/values.schema.json
M	charts/backstage/values.yaml
Falling back to patching base and 3-way merge...
Auto-merging charts/backstage/Chart.yaml
CONFLICT (content): Merge conflict in charts/backstage/Chart.yaml
Auto-merging charts/backstage/README.md
CONFLICT (content): Merge conflict in charts/backstage/README.md
Auto-merging charts/backstage/values.schema.json
Auto-merging charts/backstage/values.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 chore: update LCORE image from 0.5.2 to 0.5.3

Details

In response to this:

/cherry-pick main

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.