It is expected that VNF CSAR for K8S container multiple helm charts to support various resources and workloads.

At the time of instantiation

-  Using helm template (in API form), replace macros using VNF profiles.

-  Using various sub plugins, talk to K8S based cloud regions via K8S API.

There are two cases to be explored.

1. Where Tiller is not present in the cloud-region:  Using helm template API in K8S plugin and making K8S API or OVN/other-networking API (above approach).
2. Where Tiller is present in the cloud-region (Stretch goal):  Use tiller for all resources supported by K8S.  Resources that are meant for ONAP K8S plugin (such as onap-network),  continue to go with helm template API and call local networking subplugins. 

To support case 2, it is good to have some sort of identification (new directory in cloud specific artifact) for Multi-CLoud plugin to figure out resources that need to be consumable by K8S plugin itself.