config

History

Robert Church e923c53fa3 Armada manifest updates for chart rebase Required manifest updates to maintain current behavior: - For the keystone API continue to run as root, but adjust to new security_context override. - Turn off AppArmor profile for nova - Turn off readiness/liveness probes for nova-scheduler - Turn off readiness/liveness probes for neutron agents - Disable nova hypervisor address search that dynamically sets my_ip in nova.conf. This will interfere with per host compute override settings. Change-Id: Ic8d68da7ddf30a3a1236f01dd4eb2531efbd2965 Depends-On: Ied38e5cbedbe06fd0b6f27612aa0bddf60064dea Story: 2004520 Task: 29966 Signed-off-by: Robert Church <robert.church@windriver.com>		2019-04-08 22:33:05 -04:00
..
applications/stx-openstack/stx-openstack-helm	Armada manifest updates for chart rebase	2019-04-08 22:33:05 -04:00
helm-charts	Move the image specification to the armada manifest	2019-04-05 13:25:06 -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".