Skip to content

docs: add migration guide from backstage chart (1.y) to rhdh chart (2.y) [RHIDP-16514] - #516

Draft
rm3l wants to merge 5 commits into
redhat-developer:mainfrom
rm3l:RHIDP-16514--create-1-y-to-2-y-migration-guide-and-tooling-for-rhdh-helm-chart-users
Draft

docs: add migration guide from backstage chart (1.y) to rhdh chart (2.y) [RHIDP-16514]#516
rm3l wants to merge 5 commits into
redhat-developer:mainfrom
rm3l:RHIDP-16514--create-1-y-to-2-y-migration-guide-and-tooling-for-rhdh-helm-chart-users

Conversation

@rm3l

@rm3l rm3l commented Sep 2, 2026

Copy link
Copy Markdown
Member

Description of the change

Migration guidance with a complete values mapping reference for moving from the legacy backstage chart (RHDH 1.y) to the new redhat-developer-hub chart (RHDH 2.y).

The guide covers:

  • Step-by-step migration instructions (export old values, translate paths, helm upgrade in place)
  • Key structural changes (template ownership, system env vars, init container model, lightspeed rebranding)
  • Exhaustive values mapping tables organized by section

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

How to test changes / Special notes to the reviewer

Documentation-only change. Review the mapping tables in docs/migration-from-backstage-chart.md against the values.yaml files of both charts for accuracy.

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.

rm3l added 2 commits September 2, 2026 17:55
Add a values mapping reference under docs/ covering all path changes
between the legacy backstage chart and the new redhat-developer-hub
chart. Link to it from the README migration section and replace the
WIP placeholder with actionable guidance.

Ref: RHIDP-16514
- Use GitHub alert syntax for the important notice
- Guide users to locate their existing values file first
- Use helm upgrade --install to handle both existing and new releases

Ref: RHIDP-16514
@rm3l
rm3l force-pushed the RHIDP-16514--create-1-y-to-2-y-migration-guide-and-tooling-for-rhdh-helm-chart-users branch from 31d9627 to 010b9a4 Compare September 2, 2026 16:02
@rm3l rm3l changed the title docs: add migration guide from backstage chart (1.y) to rhdh chart (2.y) docs: add migration guide from backstage chart (1.y) to rhdh chart (2.y) Sep 2, 2026
@rm3l
rm3l force-pushed the RHIDP-16514--create-1-y-to-2-y-migration-guide-and-tooling-for-rhdh-helm-chart-users branch from 0388cd0 to 6ebc267 Compare September 2, 2026 16:12
rm3l added 2 commits September 2, 2026 21:19
Match the old backstage chart's nameOverride so that resource names
(and OpenShift Route URLs) are preserved during migration.

Ref: RHIDP-16514
@sonarqubecloud

sonarqubecloud Bot commented Sep 2, 2026

Copy link
Copy Markdown

@rm3l rm3l changed the title docs: add migration guide from backstage chart (1.y) to rhdh chart (2.y) docs: add migration guide from backstage chart (1.y) to rhdh chart (2.y) [RHIDP-16514] Sep 2, 2026
@openshift-ci

openshift-ci Bot commented Sep 2, 2026

Copy link
Copy Markdown

PR needs rebase.

Details

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.

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.

1 participant