From 24529c0f64e5ed5f8af13d76e8ef03168dc82d52 Mon Sep 17 00:00:00 2001 From: Robert Fekete Date: Wed, 3 Jul 2024 10:11:48 +0200 Subject: [PATCH 1/2] Unrelated fixes --- config/_default/config.toml | 8 ++++---- content/docs/examples/splunk.md | 2 +- content/docs/whats-new/_index.md | 6 +++--- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/config/_default/config.toml b/config/_default/config.toml index 8d80ccd5d..cdda43bb0 100644 --- a/config/_default/config.toml +++ b/config/_default/config.toml @@ -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] @@ -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 ####################### diff --git a/content/docs/examples/splunk.md b/content/docs/examples/splunk.md index 33fd668af..ba7e4f9a3 100644 --- a/content/docs/examples/splunk.md +++ b/content/docs/examples/splunk.md @@ -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 diff --git a/content/docs/whats-new/_index.md b/content/docs/whats-new/_index.md index 51a8458c2..2c9cc76cf 100644 --- a/content/docs/whats-new/_index.md +++ b/content/docs/whats-new/_index.md @@ -30,11 +30,11 @@ 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 @@ -42,7 +42,7 @@ You can now specify `configCheck` settings globally in the Loggings CRD, and ove ### 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 From 077feeb5eb58a5b2e4548731a148656b3e6a12c3 Mon Sep 17 00:00:00 2001 From: Robert Fekete Date: Wed, 3 Jul 2024 10:12:40 +0200 Subject: [PATCH 2/2] Add cookie consent banner --- layouts/partials/hooks/head-end.html | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/layouts/partials/hooks/head-end.html b/layouts/partials/hooks/head-end.html index 3e82f89b0..f6ec1c257 100644 --- a/layouts/partials/hooks/head-end.html +++ b/layouts/partials/hooks/head-end.html @@ -18,4 +18,16 @@ await import('/pagefind/pagefind-highlight.js'); new PagefindHighlight({ highlightParam: "highlight" }); -{{ end -}} \ No newline at end of file +{{ end -}} + + + +