config

History

Mario Alfredo Carrillo Arevalo e8e0c74292 Remove V1 from FM endpoint This change is required to enable the FM panels in the containerized horizon. The fmclient dependency used by the back-end already includes the reference to "v1". Then "v1" should not be part of the endpoint. Story: 2004008 Task: 34183 Change-Id: Ibe92d942b2847ef6d9271595fcc9ac2faad2fb13 Co-authored-by: Sun Austin <austin.sun@intel.com> Signed-off-by: Mario Alfredo Carrillo Arevalo <mario.alfredo.c.arevalo@intel.com>		2019-06-20 20:18:39 +00:00
..
applications/stx-openstack/stx-openstack-helm	Remove V1 from FM endpoint	2019-06-20 20:18:39 +00:00
helm-charts	Revert "Openstack clients helm chart"	2019-06-18 20:32:43 +03:00
platform/stx-platform/stx-platform-helm	Enable ceph-audit to run even if stx-openstack is not running	2019-06-03 15:46:00 -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".