starlingx/config
Code Issues Proposed changes
c3607b574d
config/kubernetes
History
Matt Peters b2f66d01ac ipv6 cluster networking support 
Addresses several issues with deploying IPv6 based network deployments:
  - kubelet node IP assignment for IP version detection
  - calico upversion to fix router ID generation from hash
  - calico configuration specific to IPv6
  - multus configuration specific to IPv6
  - ansible bootstrap playbook updates to wrap IPv6 addresses
  - ansible bootstrap updated to use Jinja2 templates
  - puppet configuration for platform services with IPv6 addresses
  - IPv4 and IPv6 IP forwarding sysctl setup
  - docker registry does not support URL encoded IPv6
  - armada does not support IPv6 address binding

NOTE:
The Puppet ERB templates were updated to maintain config_controller
functionality, but the files moved to Jinja2 templates should be removed
once config_controller is completely removed.

Change-Id: I815035c679e61250099c74b1239f19bcc72733a0
Depends-On: https://review.opendev.org/662292
Closes-Bug: #1830779
Signed-off-by: Matt Peters <matt.peters@windriver.com>
2019-05-31 14:52:43 -04:00
..
applications/stx-openstack/stx-openstack-helm Merge "Add "allow_resize_to_same_host=true" to nova chart" 2019-05-31 15:41:19 +00:00
helm-charts ipv6 cluster networking support 2019-05-31 14:52:43 -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".