restore v1alpha1, v1alpha2 and move v1alpha6 to v1alpha5 by gazarenkov · Pull Request #2727 · redhat-developer/rhdh-operator

gazarenkov · 2026-04-26T17:48:34Z

Description

restore versions v1alpha1, v1alpha2
make versions v1alpha1, v1alpha2, v1alpha3 unserved and deprecated
move new fields (Flavours) to v1alpha5 and make it (back) storage version
remove v1alpha6

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

https://redhat.atlassian.net/browse/RHDHBUGS-2993

PR acceptance criteria

Tests
Documentation

Co-authored-by: gazarenkov <gazarenkov@users.noreply.github.com>

github-actions · 2026-04-26T17:49:49Z

⚠️ Files changed in bundle and installer generation!

Those changes to the operator bundle/installer manifests 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.

…h-deprecated-alpha123 # Conflicts: # bundle/rhdh/manifests/backstage-operator.clusterserviceversion.yaml

…alpha123' into update-v1aplha5-with-deprecated-alpha123 # Conflicts: # bundle/backstage.io/manifests/backstage-operator.clusterserviceversion.yaml

Co-authored-by: gazarenkov <gazarenkov@users.noreply.github.com>

github-actions · 2026-04-26T17:54:52Z

⚠️ Files changed in bundle and installer generation!

Those changes to the operator bundle/installer manifests 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.

github-actions · 2026-04-26T17:59:27Z

PR images are available:

rhdh-qodo-merge · 2026-04-27T08:44:31Z

Code Review by Qodo

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

Context used

✅ Tickets: 🎫 RHDH upgrade to 1.10 will fail if CRD status contains v1alpha1 or v1alpha2 as storedVersion

1. Realistic DB password examples 📘 Rule violation § Compliance

Description

New comments/documentation include password-like example values (e.g., `POSTGRES_PASSWORD:
rl4s3Fh4ng3M4`) that could be mistaken for real secrets. This violates the requirement to use
clearly non-sensitive dummy values in examples.

Code

api/v1alpha1/backstage_types.go[R45-54]

+	// Name of the secret for database authentication. Optional.
+	// For a local database deployment (EnableLocalDb=true), a secret will be auto generated if it does not exist.
+	// The secret shall include information used for the database access.
+	// An example for PostgreSQL DB access:
+	// "POSTGRES_PASSWORD": "rl4*********4"
+	// "POSTGRES_PORT": "5432"
+	// "POSTGRES_USER": "postgres"
+	// "POSTGRESQL_ADMIN_PASSWORD": "rl4*********4"
+	// "POSTGRES_HOST": "backstage-psql-bs1"  # For local database, set to "backstage-psql-<CR name>".
+	AuthSecretName string `json:"authSecretName,omitempty"`

Relevance

⭐⭐⭐ High
Repo previously removed/shunned shipping secret-ish examples; compliance likely enforced for dummy
secret values.
PR-#1143
PR-#1567

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
PR Compliance ID 18 requires example secret values to be clearly fake; the added documentation shows
realistic password strings for PostgreSQL secret keys. The same values are also rendered into the
shipped CRD manifest text, amplifying the risk of accidental reuse.
Rule 18: Use only clearly non-sensitive dummy values in example secrets and dependent resources
api/v1alpha1/backstage_types.go[45-54]
config/crd/bases/rhdh.redhat.com_backstages.yaml[285-290]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Example secret values look like plausible real credentials (e.g., `rl4s3Fh4ng3M4`) and must be replaced with clearly non-sensitive placeholders.

## Issue Context
These example values are present in API type comments and propagate into generated CRD/install manifests.

## Fix Focus Areas
- api/v1alpha1/backstage_types.go[45-54]
- config/crd/bases/rhdh.redhat.com_backstages.yaml[285-290]
- bundle/rhdh/manifests/rhdh.redhat.com_backstages.yaml[285-290]
- dist/rhdh/install.yaml[297-302]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

2. Compat test uses v1alpha3 🐞 Bug ☼ Reliability

Description

The CRD now marks v1alpha3 as unserved (served: false), but
integration_tests/cr-compatibility_test.go still creates a Backstage CR using the v1alpha3 API and
asserts Create() succeeds. This test will fail when run against the current CRD (e.g., on a real
cluster running this operator/CRD).

Code

config/crd/bases/rhdh.redhat.com_backstages.yaml[R749-755]

+    served: false
    storage: false
    subresources:
      status: {}
-  - name: v1alpha4
+  - deprecated: true
+    deprecationWarning: v1alpha3 is not served
+    name: v1alpha3

Relevance

⭐⭐⭐ High
Team maintains CR compatibility tests; if v1alpha3 becomes unserved, test must switch versions to
stay valid.
PR-#1451
PR-#1479

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
Because v1alpha3 is explicitly unserved in the CRD, the apiserver will not accept create/update
requests using apiVersion=rhdh.redhat.com/v1alpha3, but the integration test still attempts to
create such a CR and expects success.
config/crd/bases/rhdh.redhat.com_backstages.yaml[749-755]
integration_tests/cr-compatibility_test.go[47-76]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The integration compatibility test creates a Backstage resource with api/v1alpha3, but v1alpha3 is now unserved in the CRD, so the create call will fail on clusters running the updated CRD.

### Issue Context
v1alpha3 is intentionally present only for storedVersions compatibility, not for serving new requests.

### Fix Focus Areas
- integration_tests/cr-compatibility_test.go[47-76]

### Suggested fix
Change the backward-compat portion of the test to create a Backstage resource using the oldest *served* version (currently v1alpha4) OR rework the test to apply an older CRD/operator first (that serves v1alpha3), create the v1alpha3 CR, then upgrade to this CRD and validate reconciliation still works.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

3. Docs still reference v1alpha6 🐞 Bug ⚙ Maintainability

Description

docs/dynamic-plugins.md still contains an example Backstage CR using apiVersion
rhdh.redhat.com/v1alpha6, but v1alpha6 is no longer present in the CRD versions list. Users
following this snippet will hit an API version-not-served / no-match error.

Code

docs/dynamic-plugins.md[30]
+apiVersion: rhdh.redhat.com/v1alpha5

Relevance

⭐⭐⭐ High
Docs apiVersion correctness is enforced in reviews; past PRs accepted updating Backstage CR examples
to current version.
PR-#1670
PR-#1943
PR-#2717

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The documentation snippet still instructs using v1alpha6, while the shipped CRD declares v1alpha5 as
the latest served/storage version (and does not include v1alpha6).
docs/dynamic-plugins.md[63-66]
config/crd/bases/rhdh.redhat.com_backstages.yaml[1653-1654]
config/crd/bases/rhdh.redhat.com_backstages.yaml[2166-2169]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
A remaining docs example uses apiVersion rhdh.redhat.com/v1alpha6 even though v1alpha6 is removed from the CRD.

### Issue Context
The PR updates some docs occurrences already, but this later snippet still references the removed version.

### Fix Focus Areas
- docs/dynamic-plugins.md[63-66]

### Suggested fix
Update the YAML snippet to use `apiVersion: rhdh.redhat.com/v1alpha5` (or the desired served version), matching the CRD versions shipped in this PR.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

rhdh-qodo-merge · 2026-04-27T08:58:07Z

Review Summary by Qodo

Restore v1alpha1 and v1alpha2, deprecate v1alpha3, and promote v1alpha5 as storage version

✨ Enhancement 📝 Documentation

Walkthroughs

Description

• Restored v1alpha1 and v1alpha2 API versions with simplified schemas, marked as unserved and
  deprecated
• Marked v1alpha3 as unserved and deprecated
• Moved Flavours field to v1alpha5 and designated it as the storage version
• Removed v1alpha6 API version entirely
• Updated all documentation, examples, and configuration files to use v1alpha5 as the current API
  version
• Updated CRD manifests and bundle configurations to reflect the new API version hierarchy
• Removed container-specific fields (Containers, FileObjectRef, PvcRef) from earlier API
  versions
• Added Replicas, Image, and ImagePullSecrets fields to Application in v1alpha2
• Updated controller imports and type aliases to reference v1alpha5
• Updated test data and integration test configurations to use v1alpha5

Diagram

flowchart LR
  v1a1["v1alpha1<br/>(Deprecated,<br/>Unserved)"]
  v1a2["v1alpha2<br/>(Deprecated,<br/>Unserved)"]
  v1a3["v1alpha3<br/>(Deprecated,<br/>Unserved)"]
  v1a4["v1alpha4"]
  v1a5["v1alpha5<br/>(Storage)"]
  v1a6["v1alpha6<br/>(Removed)"]
  
  v1a1 -- "restored" --> v1a2
  v1a2 -- "restored" --> v1a3
  v1a3 -- "marked deprecated" --> v1a4
  v1a4 -- "add Flavours" --> v1a5
  v1a6 -- "removed" --> v1a5

File Changes

1. api/v1alpha1/backstage_types.go ✨ Enhancement +288/-0

Restore v1alpha1 API version with simplified schema

• Created new v1alpha1 API version with simplified schema (no Monitoring, Deployment.Kind, Flavours,
 or container-specific fields)
• Defined core types: BackstageSpec, Application, Database, ExtraFiles, ExtraEnvs,
 ObjectKeyRef
• Added helper methods IsLocalDbEnabled(), IsRouteEnabled(), IsAuthSecretSpecified()
• Marked as unserved and deprecated version

api/v1alpha1/backstage_types.go

2. api/v1alpha1/zz_generated.deepcopy.go Miscellaneous +351/-0

Auto-generated deepcopy methods for v1alpha1 types
• Auto-generated deepcopy functions for all v1alpha1 types
• Implements deep copy semantics for nested structures and slices
api/v1alpha1/zz_generated.deepcopy.go

3. api/v1alpha1/groupversion_info.go Miscellaneous +3/-3

Define v1alpha1 group version information
• Created new file defining v1alpha1 group version schema
• Sets up GroupVersion, SchemeBuilder, and AddToScheme for v1alpha1
api/v1alpha1/groupversion_info.go

View more (48)

4. api/v1alpha2/backstage_types.go ✨ Enhancement +25/-121

Restore v1alpha2 API version with simplified schema

• Changed package from v1alpha6 to v1alpha2
• Removed Monitoring, Flavours, Deployment.Kind fields from BackstageSpec
• Removed Containers field from Env, EnvObjectRef, FileObjectRef, PvcRef types
• Simplified ObjectKeyRef (renamed from EnvObjectRef) by removing container-specific logic
• Removed FileObjectRef and PvcRef types entirely
• Added Replicas, Image, ImagePullSecrets fields to Application
• Marked as unserved and deprecated version

api/v1alpha2/backstage_types.go

5. api/v1alpha2/zz_generated.deepcopy.go Miscellaneous +31/-121

Update deepcopy methods for v1alpha2 simplified schema

• Updated package declaration from v1alpha6 to v1alpha2
• Simplified deepcopy implementations by removing container field handling
• Removed deepcopy functions for EnvObjectRef, FileObjectRef, PvcRef, Monitoring, Flavour
 types
• Updated type references to use ObjectKeyRef instead of EnvObjectRef/FileObjectRef

api/v1alpha2/zz_generated.deepcopy.go

6. api/v1alpha2/groupversion_info.go Miscellaneous +20/-0

Define v1alpha2 group version information
• Created new file defining v1alpha2 group version schema
• Sets up GroupVersion, SchemeBuilder, and AddToScheme for v1alpha2
api/v1alpha2/groupversion_info.go

7. api/v1alpha3/backstage_types.go ✨ Enhancement +2/-0

Mark v1alpha3 as unserved and deprecated
• Added //+kubebuilder:unservedversion and //+kubebuilder:deprecatedversion:warning markers
• Marked v1alpha3 as unserved and deprecated
api/v1alpha3/backstage_types.go

8. api/v1alpha5/backstage_types.go ✨ Enhancement +30/-0

Add Flavours support and mark v1alpha5 as storage version

• Added Flavours field to BackstageSpec with detailed documentation
• Created new Flavour type with Name and Enabled fields
• Added //+kubebuilder:storageversion marker to make v1alpha5 the storage version

api/v1alpha5/backstage_types.go

9. api/v1alpha5/zz_generated.deepcopy.go Miscellaneous +20/-0

Add deepcopy support for Flavours in v1alpha5
• Added deepcopy functions for Flavour type
• Updated BackstageSpec.DeepCopyInto() to handle Flavours field
api/v1alpha5/zz_generated.deepcopy.go

10. cmd/main.go ✨ Enhancement +1/-1

Update main controller to use v1alpha5 API
• Changed import from v1alpha6 to v1alpha5 as the current API version
cmd/main.go

11. api/current-types.go ✨ Enhancement +1/-1

Update current API version alias to v1alpha5
• Changed type alias import from v1alpha6 to v1alpha5
api/current-types.go

12. internal/controller/preprocessor_test.go 🧪 Tests +6/-6

Update preprocessor test to use generic API imports
• Changed import from v1alpha6 to generic api package
• Updated test code to use api.Backstage and related types instead of bsv1 prefix
internal/controller/preprocessor_test.go

13. bundle/backstage.io/manifests/rhdh.redhat.com_backstages.yaml ⚙️ Configuration changes +383/-130

Update CRD manifest with version ordering and deprecations

• Reordered API versions: v1alpha1, v1alpha2, v1alpha3, v1alpha4, v1alpha5 (storage)
• Marked v1alpha1, v1alpha2, v1alpha3 as deprecated and unserved
• Removed Monitoring, Flavours, Deployment.Kind from v1alpha2 schema
• Removed container-specific fields from v1alpha2 and v1alpha3 schemas
• Added Replicas, Image, ImagePullSecrets to v1alpha4 schema
• Added Flavours field to v1alpha5 (storage version) schema

bundle/backstage.io/manifests/rhdh.redhat.com_backstages.yaml

14. bundle/rhdh/manifests/rhdh.redhat.com_backstages.yaml ⚙️ Configuration changes +383/-130

Update RHDH bundle CRD manifest with version ordering

• Reordered API versions: v1alpha1, v1alpha2, v1alpha3, v1alpha4, v1alpha5 (storage)
• Marked v1alpha1, v1alpha2, v1alpha3 as deprecated and unserved
• Removed Monitoring, Flavours, Deployment.Kind from v1alpha2 schema
• Removed container-specific fields from v1alpha2 and v1alpha3 schemas
• Added Replicas, Image, ImagePullSecrets to v1alpha4 schema
• Added Flavours field to v1alpha5 (storage version) schema

bundle/rhdh/manifests/rhdh.redhat.com_backstages.yaml

15. bundle/rhdh/manifests/backstage-operator.clusterserviceversion.yaml ⚙️ Configuration changes +1/-39

Update CSV examples to remove deprecated versions
• Removed v1alpha3 and v1alpha6 example CRs from alm-examples
• Kept v1alpha4 and v1alpha5 examples
• Updated createdAt timestamp
bundle/rhdh/manifests/backstage-operator.clusterserviceversion.yaml

16. bundle/backstage.io/manifests/backstage-operator.clusterserviceversion.yaml ⚙️ Configuration changes +1/-39

Update CSV examples to remove deprecated versions
• Removed v1alpha3 and v1alpha6 example CRs from alm-examples
• Kept v1alpha4 and v1alpha5 examples
• Updated createdAt timestamp
bundle/backstage.io/manifests/backstage-operator.clusterserviceversion.yaml

17. docs/monitoring.md 📝 Documentation +5/-5

Update monitoring documentation examples to v1alpha5
• Updated all YAML examples from v1alpha6 to v1alpha5 API version
docs/monitoring.md

18. docs/configuration.md 📝 Documentation +4/-4

Update configuration documentation examples to v1alpha5
• Updated all YAML examples from v1alpha6 to v1alpha5 API version
docs/configuration.md

19. examples/orchestrator-cicd.yaml 📝 Documentation +1/-1

Update orchestrator-cicd example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/orchestrator-cicd.yaml

20. examples/orchestrator.yaml 📝 Documentation +1/-1

Update orchestrator example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/orchestrator.yaml

21. examples/pvc-dp-cache.yaml 📝 Documentation +1/-1

Update PVC dynamic plugins example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/pvc-dp-cache.yaml

22. examples/rhdh-cr.yaml 📝 Documentation +1/-1

Update RHDH CR example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/rhdh-cr.yaml

23. docs/lightspeed.md 📝 Documentation +1/-1

Update lightspeed documentation example to v1alpha5
• Updated YAML example from v1alpha6 to v1alpha5 API version
docs/lightspeed.md

24. examples/rhdh-cr-with-app-configs.yaml 📝 Documentation +1/-1

Update RHDH CR with app-configs example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/rhdh-cr-with-app-configs.yaml

25. examples/bs-existing-secret.yaml 📝 Documentation +1/-1

Update existing secret example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/bs-existing-secret.yaml

26. examples/envvars.yaml 📝 Documentation +1/-1

Update environment variables example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/envvars.yaml

27. examples/local-bs.yaml 📝 Documentation +1/-1

Update local Backstage example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/local-bs.yaml

28. PROJECT ⚙️ Configuration changes +2/-2

Update PROJECT file to reference v1alpha5
• Updated API path from v1alpha6 to v1alpha5
• Updated version from v1alpha6 to v1alpha5
PROJECT

29. examples/lightspeed.yaml 📝 Documentation +1/-1

Update lightspeed example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/lightspeed.yaml

30. .rhdh/docs/airgap.adoc 📝 Documentation +1/-1

Update airgap documentation example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5 in example
.rhdh/docs/airgap.adoc

31. examples/filemounts.yaml 📝 Documentation +1/-1

Update file mounts example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/filemounts.yaml

32. examples/raw-runtime-config.yaml 📝 Documentation +1/-1

Update raw runtime config example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/raw-runtime-config.yaml

33. docs/external-db.md 📝 Documentation +1/-1

Update external database documentation example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5 in example
docs/external-db.md

34. docs/dynamic-plugins.md 📝 Documentation +1/-1

Update dynamic plugins documentation example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5 in example
docs/dynamic-plugins.md

35. examples/lightspeed-disabled.yaml 📝 Documentation +1/-1

Update lightspeed-disabled example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/lightspeed-disabled.yaml

36. integration_tests/testdata/rhdh-replace-dynaplugin-root.yaml 🧪 Tests +1/-1

Update integration test data to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
integration_tests/testdata/rhdh-replace-dynaplugin-root.yaml

37. examples/bs-route-disabled.yaml 📝 Documentation +1/-1

Update route-disabled example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/bs-route-disabled.yaml

38. examples/bs-route.yaml 📝 Documentation +1/-1

Update route example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/bs-route.yaml

39. examples/catalog-index.yaml 📝 Documentation +1/-1

Update catalog-index example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/catalog-index.yaml

40. examples/bs1.yaml 📝 Documentation +1/-1

Update bs1 example to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
examples/bs1.yaml

41. integration_tests/testdata/spec-deployment.yaml 🧪 Tests +1/-1

Update integration test deployment spec to v1alpha5
• Updated Backstage CR apiVersion from v1alpha6 to v1alpha5
integration_tests/testdata/spec-deployment.yaml

42. .rhdh/scripts/prepare-restricted-environment.sh 📝 Documentation +1/-1

Update restricted environment script example to v1alpha5
• Updated example Backstage CR apiVersion from v1alpha6 to v1alpha5
.rhdh/scripts/prepare-restricted-environment.sh

43. .rhdh/scripts/install-rhdh-catalog-source.sh 📝 Documentation +1/-1

Update catalog source installation script example to v1alpha5
• Updated example Backstage CR apiVersion from v1alpha6 to v1alpha5
.rhdh/scripts/install-rhdh-catalog-source.sh

44. config/crd/bases/rhdh.redhat.com_backstages.yaml ⚙️ Configuration changes +383/-130

API version restructuring with deprecation and schema updates

• Restored deprecated API versions v1alpha1 and v1alpha2 with deprecation warnings
• Marked v1alpha1, v1alpha2, and v1alpha3 as unserved and deprecated
• Renamed v1alpha6 to v1alpha5 and made it the storage version
• Removed containers field validation from multiple configuration sections
• Removed mountPath field from PVC references and updated field descriptions
• Added new fields (image, imagePullSecrets, replicas) to deployment configuration
• Removed monitoring configuration section and kind field from deployment patch

config/crd/bases/rhdh.redhat.com_backstages.yaml

45. dist/backstage.io/install.yaml ⚙️ Configuration changes +383/-130

API version restructuring with deprecation and schema updates

• Restored deprecated API versions v1alpha1 and v1alpha2 with deprecation warnings
• Marked v1alpha1, v1alpha2, and v1alpha3 as unserved and deprecated
• Renamed v1alpha6 to v1alpha5 and made it the storage version
• Removed containers field validation from multiple configuration sections
• Removed mountPath field from PVC references and updated field descriptions
• Added new fields (image, imagePullSecrets, replicas) to deployment configuration
• Removed monitoring configuration section and kind field from deployment patch

dist/backstage.io/install.yaml

46. dist/rhdh/install.yaml ⚙️ Configuration changes +383/-130

API version restructuring with deprecation and schema updates

• Restored deprecated API versions v1alpha1 and v1alpha2 with deprecation warnings
• Marked v1alpha1, v1alpha2, and v1alpha3 as unserved and deprecated
• Renamed v1alpha6 to v1alpha5 and made it the storage version
• Removed containers field validation from multiple configuration sections
• Removed mountPath field from PVC references and updated field descriptions
• Added new fields (image, imagePullSecrets, replicas) to deployment configuration
• Removed monitoring configuration section and kind field from deployment patch

dist/rhdh/install.yaml

47. config/manifests/backstage.io/bases/backstage-operator.clusterserviceversion.yaml Additional files +0/-9

...

config/manifests/backstage.io/bases/backstage-operator.clusterserviceversion.yaml

48. config/manifests/rhdh/bases/backstage-operator.clusterserviceversion.yaml Additional files +0/-9

...

config/manifests/rhdh/bases/backstage-operator.clusterserviceversion.yaml

49. config/samples/_v1alpha3_backstage.yaml Additional files +0/-8

...

config/samples/_v1alpha3_backstage.yaml

50. config/samples/_v1alpha6_backstage.yaml Additional files +0/-8

...

config/samples/_v1alpha6_backstage.yaml

51. config/samples/kustomization.yaml Additional files +0/-2

...

config/samples/kustomization.yaml

…h-deprecated-alpha123

github-actions · 2026-04-27T13:48:28Z

PR images are available:

rm3l

I think there is another occurrence of v1alpha6 to replace in https://github.com/gazarenkov/rhdh-operator/blob/update-v1aplha5-with-deprecated-alpha123/docs/dynamic-plugins.md?plain=1#L64 (after the recent changes pushed to main).

Also, have you double-checked if there is any impact on the product docs in 1.10? If so, we would need a JIRA to track. Thanks.

…alpha123' into update-v1aplha5-with-deprecated-alpha123

sonarqubecloud · 2026-04-28T14:12:46Z

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

gazarenkov · 2026-04-28T14:13:40Z

I think there is another occurrence of v1alpha6 to replace in https://github.com/gazarenkov/rhdh-operator/blob/update-v1aplha5-with-deprecated-alpha123/docs/dynamic-plugins.md?plain=1#L64 (after the recent changes pushed to main).

Fixed

Also, have you double-checked if there is any impact on the product docs in 1.10? If so, we would need a JIRA to track. Thanks.
Could not find any entrance (seems docs is not started yet)

github-actions · 2026-04-28T14:16:24Z

PR images are available:

restore v1alpha1, v1alpha2, move v1alpha6 to v1alpha5

16af1e3

gazarenkov requested a review from rm3l April 26, 2026 17:48

gazarenkov temporarily deployed to internal April 26, 2026 17:48 — with GitHub Actions Inactive

openshift-ci Bot requested a review from subhashkhileri April 26, 2026 17:48

openshift-ci Bot added the needs-rebase label Apr 26, 2026

Regenerate bundle/installer manifests

294b0cf

Co-authored-by: gazarenkov <gazarenkov@users.noreply.github.com>

gazarenkov added 3 commits April 26, 2026 20:51

Merge remote-tracking branch 'upstream/main' into update-v1aplha5-wit…

fe8076b

…h-deprecated-alpha123 # Conflicts: # bundle/rhdh/manifests/backstage-operator.clusterserviceversion.yaml

Merge remote-tracking branch 'origin/update-v1aplha5-with-deprecated-…

56f8bdb

…alpha123' into update-v1aplha5-with-deprecated-alpha123 # Conflicts: # bundle/backstage.io/manifests/backstage-operator.clusterserviceversion.yaml

make bundle

4617ccf

gazarenkov temporarily deployed to internal April 26, 2026 17:53 — with GitHub Actions Inactive

openshift-ci Bot removed the needs-rebase label Apr 26, 2026

Regenerate bundle/installer manifests

2b2f6ac

Co-authored-by: gazarenkov <gazarenkov@users.noreply.github.com>

rm3l closed this Apr 27, 2026

rm3l reopened this Apr 27, 2026

rm3l temporarily deployed to internal April 27, 2026 08:44 — with GitHub Actions Inactive

rhdh-qodo-merge Bot reviewed Apr 27, 2026

View reviewed changes

Comment thread api/v1alpha1/backstage_types.go

rhdh-qodo-merge Bot added documentation Improvements or additions to documentation enhancement New feature or request Tests labels Apr 27, 2026

rhdh-qodo-merge Bot added the bug_fix label Apr 27, 2026

Merge remote-tracking branch 'upstream/main' into update-v1aplha5-wit…

2ab9418

…h-deprecated-alpha123

rm3l temporarily deployed to internal April 27, 2026 13:43 — with GitHub Actions Inactive

rm3l reviewed Apr 27, 2026

View reviewed changes

gazarenkov added 2 commits April 28, 2026 17:10

fix test, remove v1alpha6 occurence

bd5992e

Merge remote-tracking branch 'origin/update-v1aplha5-with-deprecated-…

92facab

…alpha123' into update-v1aplha5-with-deprecated-alpha123

gazarenkov temporarily deployed to internal April 28, 2026 14:10 — with GitHub Actions Inactive

gazarenkov requested a review from rm3l April 28, 2026 14:13

rm3l approved these changes Apr 28, 2026

View reviewed changes

openshift-ci Bot assigned rm3l Apr 28, 2026

openshift-ci Bot added the lgtm label Apr 28, 2026

openshift-merge-bot Bot merged commit 116d6c0 into redhat-developer:main Apr 28, 2026
11 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

restore v1alpha1, v1alpha2 and move v1alpha6 to v1alpha5#2727

restore v1alpha1, v1alpha2 and move v1alpha6 to v1alpha5#2727
openshift-merge-bot[bot] merged 9 commits into
redhat-developer:mainfrom
gazarenkov:update-v1aplha5-with-deprecated-alpha123

gazarenkov commented Apr 26, 2026

Uh oh!

github-actions Bot commented Apr 26, 2026

Uh oh!

github-actions Bot commented Apr 26, 2026

Uh oh!

github-actions Bot commented Apr 26, 2026

Uh oh!

rhdh-qodo-merge Bot commented Apr 27, 2026 •

edited

Loading

Uh oh!

Uh oh!

rhdh-qodo-merge Bot commented Apr 27, 2026

Uh oh!

github-actions Bot commented Apr 27, 2026

Uh oh!

rm3l left a comment

Uh oh!

sonarqubecloud Bot commented Apr 28, 2026

Uh oh!

gazarenkov commented Apr 28, 2026

Uh oh!

github-actions Bot commented Apr 28, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

gazarenkov commented Apr 26, 2026

Description

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

PR acceptance criteria

Uh oh!

github-actions Bot commented Apr 26, 2026

Uh oh!

github-actions Bot commented Apr 26, 2026

Uh oh!

github-actions Bot commented Apr 26, 2026

Uh oh!

rhdh-qodo-merge Bot commented Apr 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review by Qodo

Uh oh!

Uh oh!

rhdh-qodo-merge Bot commented Apr 27, 2026

Review Summary by Qodo

Walkthroughs

File Changes

Uh oh!

github-actions Bot commented Apr 27, 2026

Uh oh!

rm3l left a comment

Choose a reason for hiding this comment

Uh oh!

sonarqubecloud Bot commented Apr 28, 2026

Quality Gate passed

Uh oh!

gazarenkov commented Apr 28, 2026

Uh oh!

github-actions Bot commented Apr 28, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

rhdh-qodo-merge Bot commented Apr 27, 2026 •

edited

Loading