starlingx/config
Code Issues Proposed changes
fddcc4b051
config/kubernetes
History
Shuicheng Lin fddcc4b051 set wait label for nginx chart 
If wait label is not set, armada will try to wait for all the job/pod
in the same namespace, which may cause unintended consequences.
For nginx chart, there is only a GlobalNetworkPolicy set. So set the
wait resources list as empty.

Closes-Bug: 1836303

Change-Id: Ic08816b09518d09af2dad6b78a806feeeb3e9ac5
Signed-off-by: Shuicheng Lin <shuicheng.lin@intel.com>
2019-07-12 14:15:38 +08:00
..
applications/stx-openstack/stx-openstack-helm set wait label for nginx chart 2019-07-12 14:15:38 +08: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".