6e029f2a63
In the commit https://review.openstack.org/#/c/623231/, the stx branding was moved from stx-horizon to stx-gui and renamed from "titanium" to "starlingx". This updates the horizon local_settings in aramda manifests to search for "starlingx" themes in order to bring up the containerized horizon. Change-Id: I4eec0a19d808398cce4f7ec14fb93d188a9aac5a Story: 2004520 Task: 28529 Signed-off-by: Angie Wang <angie.wang@windriver.com> |
||
---|---|---|
.. | ||
applications/stx-openstack/stx-openstack-helm | ||
helm-charts/rbd-provisioner | ||
README |
The expected layout for this subdirectory is as follows: kubernetes |-- applications | `-- <application> | `-- <application>-helm RPM | `-- centos | `-- build_srpm.data | `-- <application>-helm.spec | `-- <application>-helm | `-- manifests | `-- main-manifest.yaml | `-- alt-manifest-1.yaml | `-- ... | `-- alt-manifest-N.yaml | `-- custom chart 1 | `-- Chart.yaml | `-- ... | `-- ... | `-- custom chart N | `-- Chart.yaml | `-- ... |-- helm-charts | `-- chart | `-- chart `-- README The idea is that all our custom helm charts that are common across applications would go under "helm-charts". Each chart would get a subdirectory. Custom applications would generally consist of one or more armada manifest referencing multiple helm charts (both ours and upstream ones). The application is packaged as an RPM. These application RPM are used to produce the build artifacts (helm tarballs + armada manifests) but are not installed on the system. These artifacts are extracted later for proper application packaging with additional required metadata (TBD). These applications would each get their own subdirectory under "applications".