I think that is needed to check the Kibana config, because even with Haproxy service enabled, the config is not using VIP address, as expected in this case.
(haproxy)[root@kolla-control /]# cat /etc/haproxy/haproxy.cfg
....
userlist kibanauser
user kibana insecure-password 0Aheijk4cmrGDdhllQ6eXrv8MxvbAEj3zDwzmUTS
listen kibana
bind 192.168.201.100:5601
acl auth_acl http_auth(kibanauser)
http-request auth realm basicauth unless auth_acl
server kolla-control 192.168.201.2:5601 check inter 2000 rise 2 fall 5
listen elasticsearch
option dontlog-normal
bind 192.168.201.100:9200
server kolla-control 192.168.201.2:9200 check inter 2000 rise 2 fall 5
=================================================================================================
(kibana)[kibana@kolla-control /]$ cat /opt/kibana/config/kibana.yml
kibana.defaultAppId: "discover"
server.port: 5601
server.host: "192.168.201.2"
elasticsearch.url: "http://192.168.201.2:9200"
elasticsearch.requestTimeout: 300000
elasticsearch.shardTimeout: 0
elasticsearch.ssl.verify: False
bundled_plugin_ids:
- plugins/dashboard/index
- plugins/discover/index
- plugins/doc/index
- plugins/kibana/index
- plugins/markdown_vis/index
- plugins/metric_vis/index
- plugins/settings/index
- plugins/table_vis/index
- plugins/vis_types/index
- plugins/visualize/index
Hi Carlos,
Is there any update on this? Thanks
Swapnil