Skip to content

RHDEVDOCS-3158: Allow configuration of passphrase for fluent forward #34744

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

RHDEVDOCS-3158: Allow configuration of passphrase for fluent forward #34744

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a754139
RHDEVDOCS-3158: Allow configuration of passphrase for fluent forward
vparfonov Jul 19, 2021
4f278ec
Merge branch 'openshift:main' into RHDEVDOCS-3158
rolfedh Aug 11, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 8 additions & 7 deletions modules/cluster-logging-collector-log-forward-fluentd.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,12 +36,13 @@ spec:
url: 'tls://fluentdserver.security.example.com:24224' <5>
secret: <6>
name: fluentd-secret
passphrase: phrase <7>
- name: fluentd-server-insecure
type: fluentdForward
url: 'tcp://fluentdserver.home.example.com:24224'
pipelines:
- name: forward-to-fluentd-secure <7>
inputRefs: <8>
- name: forward-to-fluentd-secure <8>
inputRefs: <9>
- application
- audit
outputRefs:
Expand All @@ -64,11 +65,11 @@ spec:
<4> Specify the `fluentdForward` type.
<5> Specify the URL and port of the external Fluentd instance as a valid absolute URL. You can use the `tcp` (insecure) or `tls` (secure TCP) protocol. If the cluster-wide proxy using the CIDR annotation is enabled, the output must be a server name or FQDN, not an IP address.
<6> If using a `tls` prefix, you must specify the name of the secret required by the endpoint for TLS communication. The secret must exist in the `openshift-logging` project and must have keys of: *tls.crt*, *tls.key*, and *ca-bundle.crt* that point to the respective certificates that they represent.
<7> Optional. Specify a name for the pipeline.
<8> Specify which log types should be forwarded using that pipeline: `application,` `infrastructure`, or `audit`.
<9> Specify the output to use with that pipeline for forwarding the logs.
<10> Optional. Specify the `default` output to forward logs to the internal Elasticsearch instance.
<11> Optional: Forward structured JSON log entries as JSON objects in the `structured` field. The log entry must contain valid structured JSON; otherwise, OpenShift Logging removes the `structured` field and instead sends the log entry to the default index, `app-00000x`.
<7> Optional: Specify the password or passphrase that protects private key file.
<8> Optional. Specify a name for the pipeline.
<9> Specify which log types should be forwarded using that pipeline: `application,` `infrastructure`, or `audit`.
<10> Specify the output to use with that pipeline for forwarding the logs.
<11> Optional. Specify the `default` output to forward logs to the internal Elasticsearch instance.
<12> Optional. One or more labels to add to the logs.
<13> Optional: Configure multiple outputs to forward logs to other external log aggregtors of any supported type:
** Optional. A name to describe the pipeline.
Expand Down