config/kubernetes
Scott Little 6f44da454d Merge remote-tracking branch starlingx/master into HEAD
Change-Id: I000b28bf01976e7c44e06ddb661d9c526a10298c
Signed-off-by: Scott Little <scott.little@windriver.com>
2019-02-22 13:28:02 -05:00
..
applications/stx-openstack/stx-openstack-helm Merge remote-tracking branch starlingx/master into HEAD 2019-02-22 13:28:02 -05:00
helm-charts Merge remote-tracking branch starlingx/master into HEAD 2019-02-20 12:03:17 -05: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".