config

History

Robert Church 12ff7c16f8 Update rbd-provisioner replicas based on installed controllers Currently the number of rbd-provisioner replicas is driven by the stx-openstack application's 'openstack-control-plane' labels. On systems where this label has not been applied to the controllers, this will result in zero provisioners being installed. Break the dependency on the stx-openstack app and set the number of replicas based on the number of installed controllers as the rbd-provisioner node selector will install in k8s masters (i.e. controllers). Also update the provisioner's storage-init pod to align with the same node selection criteria as the rbd-provisioner pod. Change-Id: Ida180fd12a4923c8cdd5bccf25a1a1e2af4f8a90 Closes-Bug: #1830290 Signed-off-by: Robert Church <robert.church@windriver.com>		2019-05-29 16:30:30 -04:00
..
applications/stx-openstack/stx-openstack-helm	enabling fm containerization log to host log files.	2019-05-29 14:16:07 +08:00
helm-charts	Update rbd-provisioner replicas based on installed controllers	2019-05-29 16:30:30 -04:00
platform/stx-platform/stx-platform-helm	Update rbd-provisioner replicas based on installed controllers	2019-05-29 16:30:30 -04: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".