Skip to content

chore(values): Update the RHDH (Backstage) Helm chart to enable Orchestrator functionality by default#157

Closed
Fortune-Ndlovu wants to merge 5 commits intoredhat-developer:mainfrom
Fortune-Ndlovu:sync-scan-rhdh-chart-with-orchestrator-enabled
Closed

chore(values): Update the RHDH (Backstage) Helm chart to enable Orchestrator functionality by default#157
Fortune-Ndlovu wants to merge 5 commits intoredhat-developer:mainfrom
Fortune-Ndlovu:sync-scan-rhdh-chart-with-orchestrator-enabled

Conversation

@Fortune-Ndlovu
Copy link
Copy Markdown
Member

@Fortune-Ndlovu Fortune-Ndlovu commented May 12, 2025

Description of the change

This PR updates the RHDH (Backstage) Helm chart to enable Orchestrator functionality by default.

Changes:

  • Set orchestrator.enabled: true in charts/backstage/values.yaml
  • Set orchestrator.serverlessLogicOperator.enabled: true
  • Set orchestrator.serverlessOperator.enabled: true

This change allows clusters to deploy the Developer Hub Orchestrator components automatically without requiring manual override of the values file.

Note:

  • No changes to the GitHub Actions Snyk workflow were necessary.

Existing or Associated Issue(s)

Additional Information

https://issues.redhat.com/browse/RHIDP-6631

Checklist

  • Chart version bumped in Chart.yaml according to semver.
  • Variables are documented in the values.yaml and added to the README.md. The pre-commit utility can be used to generate the necessary content. Use pre-commit run -a to apply changes.
  • JSON Schema template updated and re-generated the raw schema via pre-commit hook.
  • List tests pass for Chart using the Chart Testing tool and the ct lint command.

@openshift-ci openshift-ci Bot requested review from gazarenkov and tumido May 12, 2025 15:27
@Fortune-Ndlovu Fortune-Ndlovu changed the title chore(values): Update the RHDH (Backstage) Helm chart to enable Orche… chore(values): Update the RHDH (Backstage) Helm chart to enable Orchestrator functionality by default May 12, 2025
@github-actions
Copy link
Copy Markdown

⚠️ Files changed after running the pre-commit hooks

Those changes should have been pushed automatically to your PR branch.

NOTE: If the PR checks are stuck after this additional commit, manually close the PR and immediately reopen it to trigger the checks again.

@Fortune-Ndlovu
Copy link
Copy Markdown
Member Author

Fortune-Ndlovu commented May 12, 2025

/cc @rm3l

Comment thread charts/backstage/values.yaml Outdated

orchestrator:
enabled: false
enabled: true
Copy link
Copy Markdown
Member

@rm3l rm3l May 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess there was some misunderstanding.. We should not enable the Orchestrator by default (not yet at least). But the Snyk workflow can enable it explicitly when it renders the Chart.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
enabled: true
enabled: false

@Fortune-Ndlovu Fortune-Ndlovu force-pushed the sync-scan-rhdh-chart-with-orchestrator-enabled branch from 7ccfa41 to 031297d Compare May 20, 2025 09:49
…strator functionality by default.

Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
…default

Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
- Adds .github/snyk-orchestrator-values.yaml to enable Orchestrator flags
- Updates snyk.yaml to render backstage chart with Orchestrator enabled
- Ensures default values.yaml remains unchanged

Signed-off-by: Fortune-Ndlovu <fndlovu@redhat.com>
@sonarqubecloud
Copy link
Copy Markdown

@Fortune-Ndlovu
Copy link
Copy Markdown
Member Author

Closing this PR as I will create a separate Snyk project for the backstage chart with the orchestrator enabled.

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