Send logs from consul client daemonset in all Kubernetes clusters to elasticsearch
As part of investigation into dns/consul issues at gitlab-org/gitlab#271575 (closed) we discovered that the logs from the Kubernetes consul pods are not being sent to our elasticsearch infrastructure. This makes it more difficult to search and identify issues with consul running in Kubernetes, and also to correlate other issues seen in ES with issues that are affecting the consul client pods in our Kubernetes clusters.
I think we should be sending these logs to the ES index pubsub-consul-inf-${environment