config

History

yhu6 9b0820d1d6 add helm chart for nginx ports control this chart is added as a part of "stx-openstack" application, in the same chart group as openstack-ingress chart, so that when "nginx-ingress-controller" starts working, http and https ports are allowed for nginx which accepts http/https requests and forwards to internal services accordingly. In the following LP#1827246, the http request of opening console of VM instance is sent to nginx 80 first, and then nginx forwards the request to "nova-novncproxy" at port 6080 internally. Closes-Bug: 1827246 Change-Id: I183f7edc92f1a9e0bdedad0afe35e3d03e20e7d5 Signed-off-by: yhu6 <yong.hu@intel.com>		2019-06-20 00:57:50 +00:00
..
applications/stx-openstack/stx-openstack-helm	add helm chart for nginx ports control	2019-06-20 00:57:50 +00:00
helm-charts	add helm chart for nginx ports control	2019-06-20 00:57:50 +00: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".