openshift-ansible: Kibana UI is not accessible

Description

After installing Openshift logging, it’s not possible to access to Kibana UI. Here the following vars defined in the inventory regarding the Openshift logging

openshift_logging_install_logging=True
openshift_logging_es_pvc_dynamic=True
openshift_logging_es_pvc_size=50Gi

The following vars deploys EFK stack but Kibana UI is not accessible because according to the router the url is kibana.router.default.svc.cluster.local which of course is not routable from the ext. Then I tried to deploy one more time adding the following property to the inventory:

openshift_logging_kibana_hostname=kibana.apps.mydomain.net

Kibana UI is still unaccessible. When I hit https://kibana.apps.mydomain.net the browser redirects me to the internal AWS DNS name for the master (something like https://ip-10-20-5-198.us-east-2.compute.internal/oauth/authorize?response_type=code&redirect_uri=https%3A%2F%2Fkibana.apps.mydomain.net%2Fauth%2Fopenshift%2Fcallback&client_id=kibana-proxy) and of course a DNS error occurs.

NAME                                 REVISION   DESIRED   CURRENT   TRIGGERED BY
dc/logging-curator                   1          1         1         config
dc/logging-es-data-master-6pksf167   1          1         1         config
dc/logging-kibana                    1          1         1         config

NAME                                   DESIRED   CURRENT   READY     AGE
rc/logging-curator-1                   1         1         1         4m
rc/logging-es-data-master-6pksf167-1   1         1         1         8m
rc/logging-kibana-1                    1         1         1         6m

NAME                    HOST/PORT                     PATH      SERVICES         PORT      TERMINATION          WILDCARD
routes/logging-kibana   kibana.apps.mydomain.net             logging-kibana   <all>     reencrypt/Redirect   None

NAME                     CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
svc/logging-es           172.30.47.15     <none>        9200/TCP   4h
svc/logging-es-cluster   172.30.187.136   <none>        9300/TCP   4h
svc/logging-kibana       172.30.195.95    <none>        443/TCP    4h

NAME                                         READY     STATUS    RESTARTS   AGE
po/logging-curator-1-dw7g2                   1/1       Running   0          4m
po/logging-es-data-master-6pksf167-1-890cr   1/1       Running   0          8m
po/logging-fluentd-09dbk                     1/1       Running   0          3m
po/logging-fluentd-5709s                     1/1       Running   0          3m
po/logging-fluentd-9cmw5                     1/1       Running   0          3m
po/logging-fluentd-9qz2w                     1/1       Running   0          3m
po/logging-fluentd-bbd1l                     1/1       Running   0          3m
po/logging-fluentd-clwjd                     1/1       Running   0          3m
po/logging-fluentd-mffw2                     1/1       Running   0          3m
po/logging-fluentd-st559                     1/1       Running   0          3m
po/logging-kibana-1-bpn2z                    2/2       Running   0          6m
[ec2-user@ip-10-20-5-198 ~]$ oc -n logging describe svc logging-kibana
Name:                   logging-kibana
Namespace:              logging
Labels:                 <none>
Selector:               component=kibana,provider=openshift
Type:                   ClusterIP
IP:                     172.30.195.95
Port:                   <unset> 443/TCP
Endpoints:              172.16.8.22:3000
Session Affinity:       None
No events.

Version

ansible 2.2.3.0
  config file = /usr/share/ansible/openshift-ansible/ansible.cfg
  configured module search path = Default w/o overrides

openshift-ansible-3.6.85-1-8-gc5f4a60

Expected Results

Access to Kibana UI from the public network

Observed Results

Kibana UI is not accessible.