Hi guys
I'm having issues while trying to setup metricbeat on our Openshift cluster.
Here are some details:
Elasticsearch Version: 7.4
MetricBeat version: 7.4
OpenShift & Kubernetes:
(OCP) Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.14-201908291507+c406751-dirty", GitCommit:"c406751", GitTreeState:"dirty", BuildDate:"2019-08-29T22:56:42Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}
(KUBE) Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+520769a", GitCommit:"520769a", GitTreeState:"clean", BuildDate:"2019-10-11T01:55:01Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}
I managed to get the DeamonSet to run fine, and ocp workers hosts metrics are getting indexed correctly in elasticsearch.
There are 3 metricbeat pods created, 2 of the deamonset, as i have 2 workers, and 1 for the deployments, which is failing to start (In the next two posts you'll find the trace of the error, i had to split it because of the 7000 chars per post limitation)
Pods are running in custom namespace named "metricbeat".
Kube-state-metric is already deployed in openshift in the namespace named "openshift-monitoring".
I applied the changes as per documentation instructions:
https://www.elastic.co/guide/en/beats/metricbeat/current/running-on-kubernetes.html#_red_hat_openshift_configuration
I just downloaded the provided manifest and customized as per instructions above, then deployed on openshift using "oc create -f manifest.yml"
I don't know what could be the cause of this error, and i can't find anything on google to help me out...
Let me know if need more details i can provide
Have you ever encountered this issue? Can you please help me out?
Many thanks!!!!
Alessandro