Lightspeed Core Service 0.5.2

[michael-valdron]

Description of the change

Patches Lightspeed Core Service (or Lightspeed Stack) to use v0.5.2.

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

• https://redhat.atlassian.net/browse/RHIDP-14724

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.

[rhdh-qodo-merge]

PR Summary by Qodo

Bump Backstage Helm chart to Lightspeed Core Service 0.5.2

⚙️ Configuration changes 📝 Documentation 🕐 10-20 Minutes

AI Description

• Bump Backstage Helm chart version to 5.12.5.
• Update default Lightspeed Core sidecar image to lightspeed-stack:0.5.2.
• Regenerate/align schema and documentation with the new default image tag.

Diagram

graph TD
  A["Backstage Helm chart"] --> B["Chart version 5.12.5"] --> C["Default values"] --> D["Helm render"] --> E["Backstage Pod"] --> F["Lightspeed sidecar"] --> G{{"quay.io lightspeed-stack:0.5.2"}}

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Centralize LCS version as a single chart value

• ➕ Avoids updating the same version in multiple places (values + schema + docs)
• ➕ Makes future bumps less error-prone (one source of truth)
• ➖ Requires small refactor of schema/docs generation and possibly templates
• ➖ May be less explicit than a full image reference when supporting disconnected overrides

2. Use chart appVersion to track Lightspeed version (and reference it in docs)

• ➕ Clear separation: chart version vs bundled component version
• ➕ Common Helm convention for component versioning
• ➖ Still requires ensuring the actual image tag matches appVersion
• ➖ Doesn’t remove the need to set the full image ref for disconnected environments

Recommendation: Current approach is acceptable for a patch bump: it consistently updates Chart.yaml, README, values.yaml, and values.schema.json. If these bumps happen frequently, consider centralizing the Lightspeed version (or aligning via appVersion) to reduce multi-file drift and simplify future releases.

Files changed (4) +6 / -6

Documentation (1) +3 / -3

README.mdAlign docs with chart 5.12.5 and Lightspeed 0.5.2 +3/-3

Align docs with chart 5.12.5 and Lightspeed 0.5.2

• Updates the version badge and installation example to 5.12.5. Also updates the documented default Lightspeed sidecar image tag to 0.5.2.

charts/backstage/README.md

Other (3) +3 / -3

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

Bump chart version to 5.12.5

• Updates the Helm chart version from 5.12.4 to 5.12.5 to publish a new chart release containing the Lightspeed 0.5.2 default.

charts/backstage/Chart.yaml

values.schema.jsonRegenerate schema default Lightspeed image to 0.5.2 +1/-1

Regenerate schema default Lightspeed image to 0.5.2

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

charts/backstage/values.schema.json

values.yamlUpdate default Lightspeed sidecar image tag to 0.5.2 +1/-1

Update default Lightspeed sidecar image tag to 0.5.2

• Bumps the default 'global.lightspeed.sidecar.image' from 'lightspeed-stack:0.5.1' to 'lightspeed-stack:0.5.2'.

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

[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

[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: #459 failed to apply on top of branch "main":

Applying: lcs 0.5.2
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 lcs 0.5.2

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.