openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Code Issues Releases Activity

Specify 'fluentd' secret name instead of elasticsearch in LogForwarding example

Browse Source
This commit is contained in:
Michael Burke
2020-05-15 16:38:05 -04:00
committed by openshift-cherrypick-robot
parent 775c0d74a8
commit 2b378bc8f4
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
modules/cluster-logging-collector-log-forward-configure.adoc
View File

@@ -29,7 +29,7 @@ spec:
type: "elasticsearch"
endpoint: elasticsearch.openshift-logging.svc:9200
secret:
name: elasticsearch
name: fluentd
- name: elasticsearch-insecure
type: "elasticsearch"
endpoint: elasticsearch-insecure.svc.messaging.cluster.local
@@ -61,7 +61,7 @@ spec:
* Specify the type of output, either `elasticseach` or `forward`.
* Enter a name for the output.
* Enter the endpoint, either the server name or FQDN.
* Optionally, enter the name of the secret required by the endpoint for TLS communication. The secret must exist in the openshift-logging project.
* Optionally, enter the name of the secret required by the endpoint for TLS communication. The secret must exist in the openshift-logging project. For the default Elastiscearch logstore, use `fluentd` as the secret name.
* Specify `insecure: true` if the endpoint does not use a secret, resulting in insecure communication.
<5> Add one or more pipelines:
* Enter a name for the pipeline