Kibana

Versions of IBM® Cloud Private that are earlier than 3.1.2 allowed the installation of logging without Kibana, which could then be installed with a separate Helm chart. In IBM Cloud Private version 3.1.2, and later, you must use the instance of Kibana that is installed with IBM Cloud Private, if there is not a version already running from the Helm chart.

The Helm chart for ibm-icplogging-kibana was removed from IBM Cloud Private on 08-March-2019. Beginning on that date, you must enable the instance of Kibana that is provided during the installation of IBM Cloud Private, if there is not a version already running from the Helm chart.

Updating Kibana to use the embedded IBM Cloud Private instance

If your Kibana logging is configured to use the Helm chart version of Kibana, it must be reconfigured to use the installed version by completing the following steps:

1. Extract the existing Kibana chart parameters to a file named logging-values.yaml by running the following command:

   helm get values logging --tls > logging-values.yaml
   

2. Change the kibana.install parameter value of the logging-values.yaml file to true:

   kibana:
    install: true
   

3. Add the internal IBM Cloud Private Helm repository named mgmt-charts that is managed by the mgmt-repo deployment by entering the following commands:

   export HELM_HOME=~/.helm
   helm init -c --skip-refresh
   helm repo add mgmt-charts https://<cluster_CA_domain>:<cluster Master API Port>/mgmt-repo/charts --ca-file $HELM_HOME/ca.pem  --cert-file $HELM_HOME/cert.pem --key-file $HELM_HOME/key.pem
     For example, if <cluster_CA_domain> is mycluster.icp and <cluster Master API Port> is 8443.
   helm repo add mgmt-charts https://mycluster.icp:8443/mgmt-repo/charts --ca-file $HELM_HOME/ca.pem --cert-file $HELM_HOME/cert.pem --key-file $HELM_HOME/key.pem
   helm repo update
   

4. Update the logging instance to the new settings by running the following command:

   helm upgrade logging mgmt-charts/ibm-icplogging --force -f logging-values.yaml --version <version> --timeout 600 --tls
   

5. Wait about 5-10 mins and the logging with Kibana service starts. You can check the Helm upgrade status by running the following command:

    helm history --tls logging
   

Note: It is not possible to change the configuration when upgrading with the console UI. If you must use the console UI, you must completely remove and reinstall logging with the new setting.

Deploying Kibana when installing IBM Cloud Private

1. Open your config.yaml file.

2. Search for the kibana: parameter.

3. Ensure that the value is set to install: true.