Kibana ops console is not accessible

[iconoeugen]

The logging deployment is using invalid value for the template parameters KIBANA_OPS_HOSTNAME and PUBLIC_MASTER_URL:

==> default: [INFO] Creating and configuring logging
==> default: template "logging-deployer-account-template" created
==> default: template "logging-deployer-template" created
==> default: Now using project "openshift-infra" on server "https://10.2.2.2:8443".
==> default: secret/logging-deployer
==> default: --> Deploying template "logging-deployer-account-template" in project "openshift" for "logging-deployer-account-template"
==> default: --> Creating resources ...
==> default:     serviceaccount "logging-deployer" created
==> default:     serviceaccount "aggregated-logging-kibana" created
==> default:     serviceaccount "aggregated-logging-elasticsearch" created
==> default:     serviceaccount "aggregated-logging-fluentd" created
==> default:     serviceaccount "aggregated-logging-curator" created
==> default:     clusterrole "oauth-editor" created
==> default:     clusterrole "daemonset-admin" created
==> default:     rolebinding "logging-deployer-edit-role" created
==> default:     rolebinding "logging-deployer-dsadmin-role" created
==> default: --> Success
==> default:     Run 'oc status' to view your app.
==> default: --> Deploying template "logging-deployer-template" in project "openshift" for "logging-deployer-template"
==> default:      With parameters:
==> default:       MODE=install
==> default:       IMAGE_PREFIX=docker.io/openshift/origin-
==> default:       IMAGE_VERSION=v1.2.1
==> default:       IMAGE_PULL_SECRET=
==> default:       INSECURE_REGISTRY=false
==> default:       ENABLE_OPS_CLUSTER=false
==> default:       KIBANA_HOSTNAME=kibana.apps.10.2.2.2.xip.io
==> default:       KIBANA_OPS_HOSTNAME=kibana-ops.example.com
==> default:       PUBLIC_MASTER_URL=https://:8443
==> default:       MASTER_URL=https://kubernetes.default.svc.cluster.local
==> default:       ES_CLUSTER_SIZE=1
==> default:       ES_INSTANCE_RAM=8G
==> default:       ES_PVC_SIZE=
==> default:       ES_PVC_PREFIX=logging-es-
==> default:       ES_PVC_DYNAMIC=
==> default:       ES_NODE_QUORUM=
==> default:       ES_RECOVER_AFTER_NODES=
==> default:       ES_RECOVER_EXPECTED_NODES=
==> default:       ES_RECOVER_AFTER_TIME=5m
==> default:       ES_OPS_CLUSTER_SIZE=
==> default:       ES_OPS_INSTANCE_RAM=8G
==> default:       ES_OPS_PVC_SIZE=
==> default:       ES_OPS_PVC_PREFIX=logging-es-ops-
==> default:       ES_OPS_PVC_DYNAMIC=
==> default:       ES_OPS_NODE_QUORUM=
==> default:       ES_OPS_RECOVER_AFTER_NODES=
==> default:       ES_OPS_RECOVER_EXPECTED_NODES=
==> default:       ES_OPS_RECOVER_AFTER_TIME=5m
==> default:       FLUENTD_NODESELECTOR=logging-infra-fluentd=true
==> default:       ES_NODESELECTOR=
==> default:       ES_OPS_NODESELECTOR=
==> default:       KIBANA_NODESELECTOR=
==> default:       KIBANA_OPS_NODESELECTOR=
==> default:       CURATOR_NODESELECTOR=
==> default:       CURATOR_OPS_NODESELECTOR=
==> default: --> Creating resources ...
==> default:     pod "logging-deployer-2pcia" created
==> default: --> Success

[jorgemoralespou]

@iconoeugen This is because ENABLE_OPS_CLUSTER=false, so there is no OPS cluster installed. This VM is intended for developers, so there should be no need to bloat it with not developer stuff. In any case, feel free to add the option as a new adddon, so a user can select to install dev_metrics or full_metrics, if you need it. I haven't seen the value in it.

[iconoeugen]

I will create a PR to set the correct values to have a clean deployment and keep the current approach that requires the user to explicitly add ENABLE_OPS_CLUSTER=true.