From b3c05329b14a416899990a8eaedbcfb3e270e6f6 Mon Sep 17 00:00:00 2001 From: Ashwin Mehendale Date: Sun, 19 Oct 2025 18:33:21 +0530 Subject: [PATCH] OBSDOCS-235: Enable kube api-server Caching for Log Collection --- configuring/cluster-logging-collector.adoc | 2 + modules/configuring-pod-rollout-strategy.adoc | 49 +++++++++++++++++++ 2 files changed, 51 insertions(+) create mode 100644 modules/configuring-pod-rollout-strategy.adoc diff --git a/configuring/cluster-logging-collector.adoc b/configuring/cluster-logging-collector.adoc index b6b9ffdbe89e..93a2bc514d80 100644 --- a/configuring/cluster-logging-collector.adoc +++ b/configuring/cluster-logging-collector.adoc @@ -21,4 +21,6 @@ The {clo} deploys a service for each configured input receiver so that clients c include::modules/configuring-the-collector-to-receive-audit-logs-as-an-http-server.adoc[leveloffset=+2] include::modules/configuring-the-collector-to-listen-for-connections-as-a-syslog-server.adoc[leveloffset=+2] +include::modules/configuring-pod-rollout-strategy.adoc[leveloffset=+1] + //include::modules/cluster-logging-collector-tuning.adoc[leveloffset=+1] diff --git a/modules/configuring-pod-rollout-strategy.adoc b/modules/configuring-pod-rollout-strategy.adoc new file mode 100644 index 000000000000..deb3436c6a74 --- /dev/null +++ b/modules/configuring-pod-rollout-strategy.adoc @@ -0,0 +1,49 @@ +// Module included in the following assemblies: +// +// * configuring/cluster-logging-collector.adoc + + +:_newdoc-version: 2.18.4 +:_template-generated: 2025-10-19 +:_mod-docs-content-type: PROCEDURE + +[id="configuring-pod-rollout-strategy_{context}"] += Configuring pod rollout strategy + +You can configure the collector pods rollout strategy so that the requests to the API server are minimized during upgrades and restarts. + +[NOTE] +==== +Unlike in previous releases, API server kube-api caching is always enabled. +==== + +.Prerequisites +* You have administrator permissions. +* You installed the {oc-first}. +* You installed and configured {clo}. +* You have created a `ClusterLogForwarder` custom resource (CR). + +.Procedure + +. Update the `ClusterLogForwarder` CR: ++ +[source,yaml] +---- +apiVersion: observability.openshift.io/v1 +kind: ClusterLogForwarder +metadata: + name: my-forwarder + namespace: openshift-logging +spec: + collector: + maxUnavailable: +---- ++ +Where can be a number or percentage. If you do not specify a value, the default value of `100%` is used for the `maxUnavailable` field. + +. Apply the `ClusterLogForwarder` CR by running the following command: ++ +[source,terminal] +---- +$ oc apply -f .yaml +----