You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying the cluster logging for the first time it will sometimes result in an error for missing the ClusterLogging and ClusterLogForwarder.
Mon 29 Mar 2021 10:49:00 AM UTC: Checking if oc client is installed
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.6.10 True False 74d Cluster version is 4.6.10
Mon 29 Mar 2021 10:49:00 AM UTC: Deteting openshift-logging/openshift-operators-redhat namespaces if exists
Mon 29 Mar 2021 10:49:01 AM UTC: Installing the necessary objects for setting up elastic and logging operators and creating a cluster logging instance
Mon 29 Mar 2021 10:49:01 AM UTC: Creating cluster logging with custom elasticsearch backend
namespace/openshift-operators-redhat created
namespace/openshift-logging created
operatorgroup.operators.coreos.com/openshift-operators-redhat created
operatorgroup.operators.coreos.com/cluster-logging created
subscription.operators.coreos.com/cluster-logging created
unable to recognize "STDIN": no matches for kind "ClusterLogging" in version "logging.openshift.io/v1"
unable to recognize "STDIN": no matches for kind "ClusterLogForwarder" in version "logging.openshift.io/v1"
I presume this is due to trying to apply the cr's to quickly after applying the crd.
The text was updated successfully, but these errors were encountered:
When deploying the cluster logging for the first time it will sometimes result in an error for missing the ClusterLogging and ClusterLogForwarder.
I presume this is due to trying to apply the cr's to quickly after applying the crd.
The text was updated successfully, but these errors were encountered: