Skip to content
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.

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

Remove obsolete config samples for multitenant workers #1764

Merged
merged 1 commit into from
Jun 24, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -34,10 +34,6 @@ spec:
loggingRef: infra
inputTail:
storage.type: filesystem
forwardOptions:
Workers: 0
syslogng_output:
Workers: 0
positiondb:
hostPath:
path: ""
Expand Down
6 changes: 5 additions & 1 deletion config/samples/syslog-ng-simple.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,14 @@ metadata:
spec:
controlNamespace: default
fluentbit: {}
# The below network configurations allow fluentbit to retry indefinitely on a limited number of connections
# to avoid overloading the aggregator (syslog-ng in this case)
# network:
# maxWorkerConnections: 2
# syslogng_output:
# Workers: 5
# Workers: 2
# forwardOptions:
# Retry_Limit: "no_limits"
syslogNG:
globalOptions:
log_level: trace
Expand Down
5 changes: 0 additions & 5 deletions docs/logging-route.md
Original file line number Diff line number Diff line change
Expand Up @@ -92,14 +92,9 @@ metadata:
name: ops
spec:
loggingRef: ops
forwardOptions:
Workers: 0
syslogng_output:
Workers: 0
```
> Note:
> - `loggingRef`s are required here
> - `Workers: 0` is a workaround so that the processing of all tenants (outputs) don't block if one or more tenant is unavailable

And finally the logging route with a populated status:
```
Expand Down
Loading