1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-07 00:48:01 +01:00
Files
openshift-docs/modules/cluster-logging-about.adoc
2020-07-10 11:25:27 -04:00

37 lines
1.8 KiB
Plaintext

// Module included in the following assemblies:
//
// * virt/logging_events_monitoring/virt-openshift-cluster-monitoring.adoc
// * logging/cluster-logging.adoc
// * serverless/knative_serving/cluster-logging-serverless.adoc
// This module uses conditionalized paragraphs so that the module
// can be re-used in associated products.
[id="cluster-logging-about_{context}"]
= About deploying cluster logging
ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]
{product-title} cluster administrators can deploy cluster logging using
the {product-title} web console or CLI to install the Elasticsearch
Operator and Cluster Logging Operator. When the operators are installed, you create
a Cluster Logging Custom Resource (CR) to schedule cluster logging pods and
other resources necessary to support cluster logging. The operators are
responsible for deploying, upgrading, and maintaining cluster logging.
endif::openshift-enterprise,openshift-webscale,openshift-origin[]
ifdef::openshift-dedicated[]
{product-title} administrators can deploy Cluster Logging and
Elasticsearch operators via OperatorHub and configure logging in the
`openshift-logging` namespace. Configuring logging will deploy Elasticsearch,
Fluentd, and Kibana in the `openshift-logging` namespace. The operators are
responsible for deploying, upgrading, and maintaining cluster logging.
endif::openshift-dedicated[]
The Cluster Logging CR defines a complete cluster logging deployment that includes all the components
of the logging stack to collect, store and visualize logs. The Cluster Logging Operator watches the `ClusterLogging`
Custom Resource and adjusts the logging deployment accordingly.
Administrators and application developers can view the logs of the projects for which they have view access.