Re: The cluster-logging pods (Elasticsearch, Kibana, Fluentd) don't start - Openshift 4.1

2019-11-06 Thread Rich Megginson
On 11/6/19 4:51 PM, Full Name wrote: Thank you Rich for your prompt reply. After viewing the "manifests/4.2/cluster-logging.v4.2.0.clusterserviceversion.yaml " on the cluster-logging-operator pod, I confirm that the added (minKubeVersion: 1.16.0) line in GITHUB is missing in the manifest

Re: The cluster-logging pods (Elasticsearch, Kibana, Fluentd) don't start - Openshift 4.1

2019-11-06 Thread Full Name
Thank you Rich for your prompt reply. After viewing the "manifests/4.2/cluster-logging.v4.2.0.clusterserviceversion.yaml " on the cluster-logging-operator pod, I confirm that the added (minKubeVersion: 1.16.0) line in GITHUB is missing in the manifest file on the CLO pod on my Cluster. I

Re: The cluster-logging pods (Elasticsearch, Kibana, Fluentd) don't start - Openshift 4.1

2019-11-06 Thread Rich Megginson
are you running into https://bugzilla.redhat.com/show_bug.cgi?id=1766343 ? On 11/6/19 9:19 AM, Full Name wrote: Hi all, I'm trying to deploy logging on Openshift cluster 4.1.21 using the procedure described in the following link

Prometheus (OKD/3.11) NFS?

2019-11-06 Thread Alan Christie
Hi, My cluster doesn’t have dynamic volumes at the moment. For experimentation is it possible to use NFS volumes in 3.11 for prometheus and the alert manager? I notice that the ansible playbook variables for prometheus in OKD 3.11 are very different to those in 3.7 but... - Can I use