create: true name: glusterfs isDefault: false volumeType: replicate:3 reclaimPolicy: Delete volumeBindingMode: Immediate volumeNamePrefix: icp additionalProvisionerParams: {} allowVolumeExpansion: true gluster: resources: requests: cpu: 500m memory: 512Mi limits: cpu: 1000m memory: 1Gi heketi: backupDbSecret: heketi-db-backup authSecret: "heketi-secret" maxInFlightOperations: "20" dbSyncupDelay: "10" tls: generate: true issuer: "icp-ca-issuer" issuerKind: "ClusterIssuer" secretName: "" resources: requests: cpu: 500m memory: 512Mi limits: cpu: 1000m memory: 1Gi nodeSelector: key: hostgroup value: glusterfs prometheus: enabled: true path: "/metrics" port: 8080 tolerations: [] podPriorityClass: "system-cluster-critical" 

16.Also, update /opt/icp320/cluster/config.yaml file with the modifications that are listed in Example 3-23. 

Note:  When you customize the IBM Cloud Private cluster, you must set the value of the cluster_lb_address  parameter in the <icp_installation_directory>/cluster/config.yaml file to the public IP address of master node that will be accessed. And the proxy_lb_address  parameter must be set to the public IP address of proxy node. 

While you deploy ICP in your environment, ensure that the IP addresses, password, and devices are updated accordingly to fit your infrastructure. 

