Skip to content

Commit

Permalink
Merge pull request #245 from kube-logging/cookie-consent-banner
Browse files Browse the repository at this point in the history
Cookie consent banner
  • Loading branch information
fekete-robert authored Jul 3, 2024
2 parents e0229c1 + 077feeb commit 4587240
Show file tree
Hide file tree
Showing 4 changed files with 21 additions and 9 deletions.
8 changes: 4 additions & 4 deletions config/_default/config.toml
Original file line number Diff line number Diff line change
Expand Up @@ -30,10 +30,6 @@ weight = 1
section = [ "HTML", "print", "releases" ]
page = ['HTML', "releases" ]

[social]
# Used as twitter:site in page metadata
twitter = "AxoflowIO"

[markup]
[markup.goldmark]
[markup.goldmark.renderer]
Expand Down Expand Up @@ -164,6 +160,10 @@ twitter = "AxoflowIO"
icon = "fab fa-discord"
desc = "Chat with the project developers"

[params.social]
# Used as twitter:site in page metadata
twitter = "AxoflowIO"

########################
# Release versions
#######################
Expand Down
2 changes: 1 addition & 1 deletion content/docs/examples/splunk.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,11 +75,11 @@ To install the Logging operator using Helm, see [Deploy the Logging operator wit
```
1. Create a Splunk output secret from the token.
```bash
kubectl create secret generic splunk-token -n logging --from-literal "SplunkHecToken=${HEC_TOKEN}"
```
1. Define a Splunk `output`.
```bash
Expand Down
6 changes: 3 additions & 3 deletions content/docs/whats-new/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,19 +30,19 @@ Enabling disk buffers wasn't available for some of the outputs, this has been fi
### Compression support for Elasticsearch
The [Elasticsearch output of the Fluentd aggregator]({{< relref "/docs/configuration/plugins/outputs/elasticsearch.md#elasticsearch-compression_level" >}}) now supports compressing the output data using gzip. You can use the `compression_level` option use `default_compression`, `best_compression`, or `best_speed`. By default, compression is disabled.
The [Elasticsearch output of the Fluentd aggregator]({{< relref "/docs/configuration/plugins/outputs/elasticsearch.md#elasticsearch-compression_level" >}}) now supports compressing the output data using gzip. You can use the `compression_level` option to set `default_compression`, `best_compression`, or `best_speed`. By default, compression is disabled.

### Protected ClusterOutputs for Fluentd

By default, ClusterOutputs can be referenced in any Flow. In certain scenarios, this means that users can send logs from Flows to the ClusterOutput possibly spamming the output with user logs. From now on, you can set the `protected` flag for ClusterOutputs and prevent Flows from sending logs to the protected ClusterOutput.
By default, ClusterOutputs can be referenced in any Flow. In certain scenarios, this means that users can send logs from Flows to the ClusterOutput, possibly spamming the output with user logs. From now on, you can set the `protected` flag for ClusterOutputs and prevent Flows from sending logs to the protected ClusterOutput.

### ConfigCheck settings for aggregators

You can now specify `configCheck` settings globally in the Loggings CRD, and override them if needed on the aggregator level in the [Fluentd]({{< relref "/docs/configuration/crds/v1beta1/fluentd_types.md" >}}) or [SyslogNG]({{< relref "/docs/configuration/crds/v1beta1/syslogng_types.md" >}}) CRD.

### Limit connections for Fluent Bit

You can now limit the number of TCP connections that each Fluent Bit worker can open towards the aggregator endpoints. The `max_worker_connections` is set to unlimited by default, and should be used together with the `Workers` option (which defaults to 2 according to the [Fluent Bit documentation](https://docs.fluentbit.io/manual/pipeline/outputs/tcp-and-tls#:~:text=double-,Workers,-Enables%20dedicated%20thread)). The following example uses a single worker with a single connection:
You can now limit the number of TCP connections that each Fluent Bit worker can open toward the aggregator endpoints. The `max_worker_connections` is set to unlimited by default, and should be used together with the `Workers` option (which defaults to 2 according to the [Fluent Bit documentation](https://docs.fluentbit.io/manual/pipeline/outputs/tcp-and-tls#:~:text=double-,Workers,-Enables%20dedicated%20thread)). The following example uses a single worker with a single connection:

```yaml
kind: FluentbitAgent
Expand Down
14 changes: 13 additions & 1 deletion layouts/partials/hooks/head-end.html
Original file line number Diff line number Diff line change
Expand Up @@ -18,4 +18,16 @@
await import('/pagefind/pagefind-highlight.js');
new PagefindHighlight({ highlightParam: "highlight" });
</script>
{{ end -}}
{{ end -}}

<!-- Script for cookie-consent banner (https://www.sprucejoy.com/resources/cookie-consent-gdpr/) -->
<script>
window.__SJ_MESSAGE__ =
'We collect cookies to analyze our website traffic and performance. We never collect any personal data.'
window.__SJ_ACCEPT_BTN_TEXT__ = 'Accept'
window.__SJ_REJECT_BTN_TEXT__ = 'Reject'
</script>
<script
src="https://cdn.jsdelivr.net/gh/sprucejoy/cookie-consent-autoblock-gdpr/cookie-consent.js"
crossorigin="anonymous"
></script>

0 comments on commit 4587240

Please sign in to comment.