Skip to content

Commit fc87c75

Browse files
committed
feat: protected cluster outputs
Signed-off-by: Bence Csati <[email protected]>
1 parent 83a2a38 commit fc87c75

File tree

1 file changed

+41
-0
lines changed

1 file changed

+41
-0
lines changed

content/docs/configuration/output.md

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -97,3 +97,44 @@ spec:
9797
- For the details of the supported output plugins, see {{% xref "/docs/configuration/plugins/syslog-ng-outputs/_index.md" %}}.
9898
- For the details of `SyslogNGOutput` custom resource, see {{% xref "/docs/configuration/crds/v1beta1/syslogng_output_types.md" %}}.
9999
- For the details of `SyslogNGClusterOutput` custom resource, see {{% xref "/docs/configuration/crds/v1beta1/syslogng_clusteroutput_types.md" %}}.
100+
101+
## protected flag cluster outputs
102+
103+
Since versions:
104+
105+
- 4.7 for Fluentd
106+
- 5.0 for Syslog-ng
107+
108+
You can set the `protected` flag on a `ClusterOutput` and `SyslogNGClusterOutput`. This prevents namespaced `Flows` and `SyslogNGFlows` from sending logs to these outputs and only allows `ClusterFlows` and `SyslogNGClusterFlows` to reference it.
109+
110+
By default, `ClusterOutputs` can be referenced by any `Flow`. Setting the `protected` flag restricts this access to `ClusterFlows` only.
111+
112+
```yaml
113+
apiVersion: logging.banzaicloud.io/v1beta1
114+
kind: ClusterOutput
115+
metadata:
116+
name: protected-cluster-output
117+
namespace: infra
118+
spec:
119+
protected: true
120+
s3:
121+
aws_key_id:
122+
valueFrom:
123+
secretKeyRef:
124+
name: s3-secret
125+
key: awsAccessKeyId
126+
namespace: default
127+
aws_sec_key:
128+
valueFrom:
129+
secretKeyRef:
130+
name: s3-secret
131+
key: awsSecretAccessKey
132+
namespace: default
133+
s3_bucket: example-logging-bucket
134+
s3_region: eu-west-1
135+
path: logs/${tag}/%Y/%m/%d/
136+
buffer:
137+
timekey: 1m
138+
timekey_wait: 10s
139+
timekey_use_utc: true
140+
```

0 commit comments

Comments
 (0)