storageClass: logging-storage-datanode useDynamicProvisioning: false master: name: master replicas: "1" name: elasticsearch filebeat: name: filebeat-ds scope: namespaces: - production nodes: production: "true" kibana: name: kibana install: true external: logstash: name: logstash replicas: "1" security: ca: external: certFieldName: ca.crt keyFieldName: ca.key secretName: elk-ca-secret origin: external enabled: true xpack: monitoring: true These values should be tailored to meet the requirements. If dynamic provisioning is  enabled in the cluster, set  elasticsearch.data.storageClass  to the appropriate storage  class name and  elasticsearch.data.useDynamicProvisioning  value to  true. In this values file, the  kibana.external  is intentionally left empty, so that Kubernetes will  automatically assign a NodePort value from the default NodePort range. At the time of  writing, the Helm chart does not support automatic NodePort assignment when deploying  through the IBM Cloud Private catalog user interface, due to validation on empty fields.  Therefore auto-assignment is only possible by deploying the Helm chart through the Helm  CLI. Additional values not in the  override-values.yaml  can also be assigned using the  --set parameter in the  helm install  command. 5. Deploy the ibm-icplogging-2.2.0.tgz Helm chart using  helm install , passing the values  files created earlier. The values files order is important as Helm will override the values  from each file in sequence. For example, the values set in override-values.yaml will  replace any values in the default-values.yaml file as priority is given to the right-most file  specified. helm install ibm-icplogging-2.2.0.tgz --name app-logging --namespace elk -f  default-values.yaml -f override-values.yaml --tls [root@icp-ha-boot cluster]# kubectl -n elk get pods -l release=app-logging NAME READY STATUS RESTARTS AGE After some time, all resources should have been deployed to the elk namespace. To view  all pods in the release, use  kubectl -n elk get pods -l release=app-logging Chapter 5. Logging and monitoring  195