1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-07 09:46:53 +01:00
Files
openshift-docs/logging/cluster-logging-deploying.adoc

64 lines
3.3 KiB
Plaintext

:_mod-docs-content-type: ASSEMBLY
:context: cluster-logging-deploying
[id="cluster-logging-deploying"]
= Installing Logging
include::_attributes/common-attributes.adoc[]
include::_attributes/attributes-openshift-dedicated.adoc[]
toc::[]
You can deploy {logging} by installing the {clo}. The {clo} creates and manages the components of the logging stack.
include::snippets/logging-compatibility-snip.adoc[]
[IMPORTANT]
====
For new installations, use Vector and LokiStack. Elasticsearch and Fluentd are deprecated and are planned to be removed in a future release.
====
ifdef::openshift-origin[]
[id="prerequisites_cluster-logging-deploying"]
== Prerequisites
* Ensure that you have downloaded the {cluster-manager-url-pull} as shown in _Obtaining the installation program_ in the installation documentation for your platform.
+
If you have the pull secret, add the `redhat-operators` catalog to the OperatorHub custom resource (CR) as shown in _Configuring {product-title} to use Red Hat Operators_.
endif::[]
//Installing the CLO via webconsole
include::modules/cluster-logging-deploy-console.adoc[leveloffset=+1]
include::modules/create-cluster-logging-cr-console.adoc[leveloffset=+1]
// Install using CLI
include::modules/cluster-logging-deploy-cli.adoc[leveloffset=+1]
include::modules/create-cluster-logging-cli.adoc[leveloffset=+1]
[id="cluster-logging-deploying-postinstallation"]
== Postinstallation tasks
After you have installed the {clo}, you can configure your deployment by creating and modifying a `ClusterLogging` custom resource (CR).
[TIP]
====
If you are not using the Elasticsearch log store, you can remove the internal Elasticsearch `logStore` and Kibana `visualization` components from the `ClusterLogging` custom resource (CR). Removing these components is optional but saves resources. See xref:../logging/log_storage/logging-config-es-store.adoc#cluster-logging-removing-unused-components-if-no-elasticsearch_logging-config-es-store[Removing unused components if you do not use the Elasticsearch log store].
====
include::modules/cluster-logging-about-crd.adoc[leveloffset=+2]
include::modules/configuring-log-storage-cr.adoc[leveloffset=+2]
include::modules/configuring-logging-collector.adoc[leveloffset=+2]
include::modules/configuring-log-visualizer.adoc[leveloffset=+2]
include::modules/cluster-logging-deploy-multitenant.adoc[leveloffset=+2]
[role="_additional-resources"]
.Additional resources
ifdef::openshift-enterprise,openshift-origin[]
* xref:../networking/network_policy/about-network-policy.adoc[About network policy]
* xref:../networking/openshift_sdn/about-openshift-sdn.adoc[About the OpenShift SDN default CNI network provider]
* xref:../networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc[About the OVN-Kubernetes default Container Network Interface (CNI) network provider]
endif::[]
ifdef::openshift-rosa,openshift-dedicated[]
* link:https://docs.openshift.com/container-platform/latest/networking/network_policy/about-network-policy.html[About network policy]
* link:https://docs.openshift.com/container-platform/latest/networking/openshift_sdn/about-openshift-sdn.html[About the OpenShift SDN default CNI network provider]
* link:https://docs.openshift.com/container-platform/latest/networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.html[About the OVN-Kubernetes default Container Network Interface (CNI) network provider]
endif::[]