-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OBSDOCS-235: Enable kube api-server Caching for Log Collection #100794
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
Merged
briandooley
merged 1 commit into
openshift:standalone-logging-docs-main
from
theashiot:OBSDOCS-2354
Nov 4, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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: <value> | ||
| ---- | ||
| + | ||
| Where <value> 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 <filename>.yaml | ||
| ---- | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.