-
Story
-
Resolution: Won't Do
-
High
-
None
-
None
-
None
-
SDNC Fr Sp4:1/6-1/24
Helm deploy plugin deploys the sub-charts in the ascending order of names, it will cause issues when upgrading/installing any component as helm upgrade will not come out for that component until all the hooks have been executed successfully.
This will create problems when this component (say aai ) depends on any other component (like dmaap/cassandra/mariadb-galera/aaf) which has not been deployed/upgraded using 'helm upgrade' yet because they would be installed based on respective naming order, so current component (aai) would not be installed successfully as its waiting for shared resources and others will not be installed as well as their turn would not come.
The fix could be to run the helm upgrades for sub charts in parallel (https://gerrit.onap.org/r/#/c/79425/2/kubernetes/helm/plugins/deploy/deploy.sh) or installing all the components which are being used by others first in correct order.
- blocks
-
OOM-1676 Upgrade AAI to use helm hooks for rolling upgrade
- Closed