Skip to content

Commit e4fd705

Browse files
committed
RHIDP-7564 - Support Pre-Configured RHDH Deployments in Operator
1 parent 25694ca commit e4fd705

File tree

1 file changed

+37
-0
lines changed

1 file changed

+37
-0
lines changed
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
[id='proc-install-distribute-custom-flavor_{context}']
2+
= Distributing a custom flavor
3+
Custom flavors can be distributed as container images, offering a secure and versioned approach.
4+
5+
.Procedure
6+
7+
. Create a container image that contains your flavor's directory structure at a specific location, typically `/flavor/`. The image should be lightweight and contain only the necessary manifests and files.
8+
+
9+
[source,terminal,subs="+quotes"]
10+
----
11+
/flavor/
12+
├── flavor.yaml # Flavor manifest
13+
├── config/
14+
├── resources/
15+
└── hooks/
16+
----
17+
18+
. When the image is built, push it to a container registry which makes the flavor accessible to others, for example:
19+
+
20+
[source,terminal,subs="+quotes"]
21+
----
22+
podman push quay.io/myorg/my-custom-flavor:1.0.0
23+
----
24+
25+
. Users can deploy your custom flavor by referencing the container image directly in their Backstage custom resource. The operator pulls the image, extracts the contents, and applies the configuration automatically. For example:
26+
+
27+
[source,yaml,subs="+attributes"]
28+
----
29+
apiVersion: backstage.redhat.com/v1alpha1
30+
kind: Backstage
31+
metadata:
32+
name: custom-hub
33+
spec:
34+
flavor:
35+
name: my-custom-flavor
36+
image: quay.io/myorg/my-custom-flavor:1.0.0
37+
----

0 commit comments

Comments
 (0)