[standalone-logging-docs-6.0] Update LokiStack configuration with global limits for retention and managementState #102472
Conversation
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
…anagementState Doc Reference: https://docs.redhat.com/en/documentation/red_hat_openshift_logging/6.3/html/installing_logging/installing-logging#install-loki-operator-cli_installing-logging By default, the retention config is not mentioned in standard installation YAML because of which end users use the exact same config for deployment and then object storage get flooded with a lot of logs. This breaks ODF and impacts the applications consuming storage from ODF. It is required to add retention config in standard installation YAML in the documentation. If there is no retention, then the logs will not be remove / cleaned up from object storage until retention is configured or until lifecycle policy is configured on the object bucket. [new commit] Update LokiStack configuration with global limits for retention and managementState Doc Reference: https://docs.redhat.com/en/documentation/red_hat_openshift_logging/6.3/html/installing_logging/installing-logging#install-loki-operator-cli_installing-logging By default, the retention config is not mentioned in standard installation YAML because of which end users use the exact same config for deployment and then object storage get flooded with a lot of logs. This breaks ODF and impacts the applications consuming storage from ODF. It is required to add retention config in standard installation YAML in the documentation. If there is no retention, then the logs will not be remove / cleaned up from object storage until retention is configured or until lifecycle policy is configured on the object bucket. Here is the updated config: ~~~ apiVersion: loki.grafana.com/v1 kind: LokiStack metadata: name: logging-loki 1 namespace: openshift-logging 2 spec: managementState: Managed limits: global: 3 retention: 4 days: 20 # Set the value as per requirement. size: 1x.small 5 storage: schemas: - version: v13 effectiveDate: "<yyyy>-<mm>-<dd>" 6 secret: name: logging-loki-s3 7 type: s3 8 storageClassName: <storage_class_name> 9 tenants: mode: openshift-logging 10 ~~~
1 task
openshift-ci
bot
added
the
size/M
|
@openshift-cherrypick-robot: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
briandooley
merged commit 9fe6f0d
into
openshift:standalone-logging-docs-6.0
2 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This is an automated cherry-pick of #102311
/assign briandooley