summaryrefslogtreecommitdiffstats
path: root/kubernetes/helm/plugins
AgeCommit message (Collapse)AuthorFilesLines
2018-10-18Fix deploy when subcharts contain same nameMike Elliott1-6/+10
Invalid subchart override file (internal) was being created for portal. This was caused by an incorrect match on subcharts that included "portal as a prefix or suffix in its name. Change-Id: I02d9564f573cf194940df7edc267079e2fb7eec2 Issue-ID: OOM-1344 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2018-10-15Update (un)deploy helm pluginsMike Elliott2-17/+100
- Added support for deploying and undeploying individual releases. - Added support for a --verbose flag to output details during a deploy. By default, verbose output will be supressed. - Fixed issues preventng some flags from propagating to helm commands. - Fixed issue where by --set <chartname>.enabled=false was not removing disabled Helm Charts. Change-Id: I8e407808a9946f316d035efd503316f96723223d Issue-ID: OOM-1344 Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
2018-09-17Add helm plugins to (un)deploy onapMike Elliott4-0/+234
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>