New feature: setting a release name for Helm based KDUs.

Setting a release name for Helm based KDUs

Proposers

• Alexis Romero (Indra - Minsait)
• Francisco Rodríguez (Indra - Minsait)

Target MDF/TF

LCM, NBI, devops

Description

Many Helm Charts available by CNF vendors rely on the release name of the chart in order to set the name for the application components. From our experience with real CNF implementations, this scenario is more common than expected and forcing vendors to modify their tested and certified charts sometimes is not possible.

Currently, OSM supports the deployment of Helm Charts v2 and v3 generating a random name for the release.

The proposed solution is to add an additional instantiation parameter at VDU level enabling the possibility of setting the release name for a given KDU. Also, it is proposed to modify test k8s_04-openldap_helm to test this feature and check previous method is still valid

Demo of definition of done

• OSM can deploy a Helm based CNF specifying the release name at instantiation time
• Updated k8s_04-openldap_helm test runs successfully