On Wed, Nov 6, 2019 at 6:48 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
e the minKubeVersion there, but if that doesn't trigger a
redeployment, I'm not sure how to do that.
Thank you.
-Original Message-
From: "Rich Megginson" [rmegg...@redhat.com]
Date: 11/06/2019 01:21 PM
To: users@lists.openshift.redhat.com
Subject: Re: The cluster-logging pods (Elastic
ot;Rich Megginson" [rmegg...@redhat.com]
Date: 11/06/2019 01:21 PM
To: users@lists.openshift.redhat.com
Subject: Re: The cluster-logging pods (Elasticsearch, Kibana, Fluentd) don't
start - Openshift 4.1
are you running into https://bugzilla.redhat.com/show_bug.cgi?id=1766343 ?
On 11/6/19
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
