config

History

Kristine Bujold ed58a22e03 Move cinder static config to Armada manifest Move cinder static configuration from the overrides to the Armada manifest. Story: 2003909 Task: 29419 Change-Id: I5e213eb4dff5c3e1f2ef1edd588e60fb11501125 Signed-off-by: Kristine Bujold <kristine.bujold@windriver.com>		2019-02-08 16:50:31 -05:00
..
applications/stx-openstack/stx-openstack-helm	Move cinder static config to Armada manifest	2019-02-08 16:50:31 -05:00
helm-charts	Add helm chart for galera arbitrator	2019-01-30 14:46:35 -06:00
README	Enable StarlingX helm charts for stx-openstack app	2018-11-07 16:14:42 -05:00

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".