config

History

Bart Wensley 6790b7e7c7 Replicate nova-api-proxy pod The nova-api-proxy is currently running in a single pod on one of the controllers. To improve recovery time when a controller fails, the nova-api-proxy pod will now be run with replicas set to two and anti-affinity configured so there is a pod on each controller. Closes-bug: 1833730 Change-Id: Iacd17251b86050e337d9a0f832b9dfa6e9864fce Signed-off-by: Bart Wensley <barton.wensley@windriver.com>		2019-07-24 09:54:16 -05:00
..
applications/stx-openstack/stx-openstack-helm	Replicate nova-api-proxy pod	2019-07-24 09:54:16 -05: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".