diff options
author | Mike Elliott <mike.elliott@amdocs.com> | 2018-09-17 14:41:40 -0400 |
---|---|---|
committer | Mike Elliott <mike.elliott@amdocs.com> | 2018-09-17 15:06:15 -0400 |
commit | 0dfcc9f8a1a57eecc67b9388aa3da7c6f1263f3d (patch) | |
tree | 795b521c2f2ada8fca6c15aeaf4b58a2c0ce4511 /kubernetes/dmaap | |
parent | bc7c2b8308105985d2807a1ddd94537b5b6bbbd3 (diff) |
Add helm plugins to (un)deploy onap
In the Casablanca release, ONAP has become very large.
Every Helm chart contains some amount of external configuration.
And unfortunately, there is a limit to the amount of configuration that
can exist in a Helm chart. When ONAP is installed as a unbrella chart
containing many subcharts (each with configuration), the
amount of configuration that resides in configmaps in K8s
causes the installation to fail. To work around this issue, it was
necessary to introiduce a Helm plugin that will install/upgrade onap
by deploying the parent chart and each subchart within its own
Helm "release". This is the initial version of the plugins, which
has been verified to work and unblock integration in the deployment
of all of ONAP. Improvements will be made post M4 to further harden
and enhance the plugins. Specifically, the plugins are not currently
resilent to network issues which can cause some of the subcharts to
fail to deploy. To work around this, the plugins should be run from
within the same network as the k8s cluster you are deploying to.
To install, copy plugins directory into your local ~/.helm/ folder.
After which you should see 'deploy' and 'undeploy' if you do a 'helm'
with no arguments.
Change-Id: I7c586f1c75f7249d2d7c38b4088129162c96401d
Issue-ID: OOM-1344
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
Diffstat (limited to 'kubernetes/dmaap')
0 files changed, 0 insertions, 0 deletions