...

For k8s plugin, a SubPlugin for k8s will be developered which will invoke the provided APIs to do definition and Upload.

How to implement? 

the sequence flow of sdc client:

For each notification while user clicks the “Service distribution"

• gets the Service Metadata
• For each Resource Instance (e.g. a VF instance which appears to correlate with a VF Module from what I’ve seen so far)
• For each Artifact in the artifact list of Resource
  • If artifact type is VF_MODULE_METADATA
    • create a dir with the name of “vfmodule-model-customization-id”
    • download the artifact's content and store it, may name it as metadata.sjon there
    • parse the artifact content to get all UUIDs that are listed in artifact list under its UUID's dir. 
  • If artifact is HEAT, HEAT_ENV, CLOUD_TECHNOLOGY_*
    • Store all the artifacts with the name of  UUID under VF_MODULE_METADATA's UUID dir
  • if there is sub-plugin configuration, 
    • yes, suppose k8s in R4, a sub-plugin will do definition and upload based on the APIs provided by k8s
    • no, there is no sub-plugin to be used. the plugin of Multicloud will use shared folder method to get all artifacts and parse the metadata.json file.

SDC class implementation

According to the SDC Project's documentation: SDC Distribution client AID, the client needs to register as a SDC client, and acts as a publisher too then publish the distribution status event.

...