Create ONAP deployment
...
The upgrade workflow is for individual components. So we should provide node_instance_id to identify the component. User can get node_instance_id from "Nodes" section.
| Input | description | default value |
|---|---|---|
| node_instance_id | The unique id of onap component | N/A |
| chartRepo | The URL of helm repo | N/A |
| chartVersion | The helm chart version | N/A |
| config_json | The JSON format config overwrite. This method is suitable for small amount config change. Leave it empty, if use config_url. | N/A |
| config_url | The URL of the overwrite config file. This method is suitable for large amount config change. Leave it empty, if use config_json. | N/A |
| config_format | if use config_url, please provide the type of file. json or yaml | json |
Rollback
The Rollback workflow can rolls back an ONAP component to a previous revision.
| Input | description | default value |
|---|---|---|
| node_instance_id | The unique id of onap component | N/A |
| revision | revision (version) number of onap component. User can find it in "helm-history"
| N/A |
Uninstall
The Uninstall workflow will delete all the helm deployment form K8s cluster.
