Successfully packaged chart and saved it to: /root/ACE/ace-helm-master/ibm-ace-bar-dev-1.0.0.tgz 

7. Load the helm chart in the Cloud Pak catalog: 

Note:  This requires the Cloud Pak CLI to be installed as specified in 5.1.4, “Getting access to IBM Cloud Pak for Integration for the exercises” on page 145. 

# cloudctl login -a https://mycluster.icp:8443 –skip-ssl-validation # kubectl load-helm-chart –archive ibm-ace-bar-dev-1.0.0.tgz –clustername mycluster.icp Loading helm chart {“url”:”https://icp-management-ingress:8443/helm-repo/charts/index.yaml”} OK Synch charts {“message”:”synch started”} OK 

8. The chart that was just published will now be seen in the Cloud Pak admin console, in the Catalog. Use ‘local-charts’ as a filter in the Catalog menu. 

## Using helm chart metadata 

Cloud Pak catalog provides some other features to make the helm charts easier to use. One of these features is formatting and validating the values that the chart makes available for users to customize. 

You can define metadata for the parameters in values-metadata.yaml  file that is placed in root directory of the chart (same as values.yaml) . The file values-metadata.yaml defines the metadata for values defined in values.yaml. It should mirror the same structure of values.yaml, except that instead of specifying a value for the leaf property, define a property named __ metadata . 

If the values-metadata.yaml file is not present, the UI continues to display all parameters that are declared in values.yaml based on the type inference. See Example 7-1. 

example: __metadata: label: Example description: New Version stringField: __metadata: label: String field type: string required: true numberField: __metadata: label: Number field (with validation) type: number required: true 

