docker build -t ace11005 --build-arg  ACE_INSTALL=11.0.0-ACE-LINUXX64-FP0005.tar.gz --file ubi/Dockerfile.aceonly  . You can also refer to the instruction on  https://github.com/ot4i/ace-docker  to  ensure that you get the most current syntax for building the IBM App Connect Docker  images. f. Log in to Docker registry and push the Docker image to your private registry of your  Cloud Pak for Integration platform.  4. Create a helm chart by modifying  values.yaml  and  service.yaml  files to include  additional fields for the switch ports that we want to expose. a. As shown in Example 7-6 we add the new fields named switch* under service type  NodePort in values.yaml file. Example 7-6 Additional service ports in values.yaml Example 7-7 New port fields in service.yaml file docker login mycluster.icp:8500  docker tag ace11005:latest  mycluster.icp:8500/icp4i/ibm-ace-server-prod:11.0.0.5 docker push mycluster.icp:8500/icp4i/ibm-ace-server-prod:11.0.0.5 type: NodePort webuiPort: 7600 serverlistenerPort: 7800 serverlistenerTLSPort: 7843 switchport1: 9010 switchport2: 9011 switchport3: 9012 b. Add corresponding entries in  service.yaml  as shown in Example 7-7. service: - port: {{ .Values.service.switchport1 }} targetPort: {{ .Values.service.switchport1 }} protocol: TCP name: switchport1 - port: {{ .Values.service.switchport2 }} targetPort: {{ .Values.service.switchport2 }} protocol: TCP name: switchport2 - port: {{ .Values.service.switchport3 }} targetPort: {{ .Values.service.switchport3 }} protocol: TCP name: switchport3 c. Update  chart.yaml  file to specify the new version number of the chart. For example: version: 1.1.2-icp4i-07 d. Package and upload the helm chart. For this you will need to have the Cloud Pak CLI  installed as specified in 5.1.4, “Getting access to IBM Cloud Pak for Integration for the  exercises” on page 145. Chapter 7. Field notes on modernization for application integration  519