9a749f1d80
Use an application RPM to build and collect application artifacts. This follows the same mechanism that is used to build the openstack-helm and openstack-helm-infra charts. The custom StarlingX charts are built and the application specific armada manifests are included in the RPM. This application RPM will be used to produce some of the required build artifacts (custom helm tarballs + armada manifests) but is not intended to be installed on the system. These artifacts are extracted later for proper application packaging with additional required metadata. Changes also include: - Update the README describing the new layouts for applications. - Move the nova-api-proxy chart from the common area to be included as a chart specific to the stx-openstack app. Change-Id: I1140760d56035249324519be93bb913e18f394d9 Story: 2004005 Task: 27801 Depends-On: I57c5ec5f3565e9e585f0935af745e495699aa28c Signed-off-by: Robert Church <robert.church@windriver.com>
40 lines
1.4 KiB
Plaintext
40 lines
1.4 KiB
Plaintext
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".
|