For example: helm package ibm-ace-server-icip-prod cloudctl catalog load-chart -a ibm-ace-server-icip-prod-1.1.2-icp4i-07.tgz Note:  In future releases of ICP4I, you might be able to add the agent and switch files  dynamically via Kubernetes secrets generated by using the generateSecrets.sh script.  In this case, you will not have to build a custom Docker image and helm chart for  deploying Switch and Connectivity Agent components. Starting switch with config folder: '/home/aceuser/ace-server/config/iibswitch/switch' The Switch server has started listening for agent requests on the back side port '9010'. The Switch server has started listening for agent requests on the front side port '9011'. The Switch server has started listening for HTTPS administration requests on port '9012'. The integration server component 'switch' has been started. component started: "switch" 8. From the services details of the helm release find out the corresponding externally  exposed port numbers as shown in Figure 7-85. 7. Upon successful deployment of helm release, you will find messages as shown in  Example 7-8 in the integration server log (through Kibana logging service). The console  output shows the port numbers that the Switch server is listening on. 520  Accelerating Modernization with Agile Integration Figure 7-84 Docker image field Figure 7-83 Helm chart version selection 6. Select the Docker image that we created in step 3 and select the appropriate image tag as  shown in Figure 7-84. Example 7-8 Console output for switch server 5. Now deploy the integration server to host Switch server by selecting the new helm chart  version from the drop-down list as shown in Figure 7-83. 