config

History

Al Bailey 5c716a45a0 Build stx-openstack-helm without requiring networking This commit bypasses the helm init --client-only command which required networking access from within mock. This allows stx-openstack-helm to be built the same as other std packages Story: 2004005 Task: 28794 Change-Id: I113ec91b64faebf2e7e8154e4bfbe75acc3fbf43 Depends-On: I35c9b547a98fac559793bc2ec00012f6eded8ffa Signed-off-by: Al Bailey <Al.Bailey@windriver.com>		2019-01-08 13:13:13 -06:00
..
applications/stx-openstack/stx-openstack-helm	Build stx-openstack-helm without requiring networking	2019-01-08 13:13:13 -06:00
helm-charts/rbd-provisioner	Enhancements for the rbd-provisioner helm chart	2018-12-13 19:13:15 +00: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".