starlingx
/
config
Code Issues Proposed changes
config/kubernetes
History
zhipengl 707cdd9d68 Expose the novncproxy port 
The novncproxy would be available at the OAMIP:30680.

Test pass on simplex setup.
VM console can be accessed through horizon.

Closes-bug: 1827246

Depends-on: https://review.opendev.org/#/c/684443/
Change-Id: I6c450d391a8842d8336a0085dc31f939cb8789d9
Signed-off-by: zhipengl <zhipengs.liu@intel.com>
(cherry picked from commit f8ec30d0c6)
 		2019-09-25 18:44:09 +08:00
..
applications/stx-openstack/stx-openstack-helm Expose the novncproxy port 2019-09-25 18:44:09 +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".