Skip to content

Conversation

@prithvipatil97
Copy link
Contributor

@prithvipatil97 prithvipatil97 commented Nov 12, 2025

Documentation Link:
https://docs.redhat.com/en/documentation/red_hat_openshift_logging/6.3/html/installing_logging/installing-logging#installing-loki-operator-web-console_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

Version(s):

Logging 6.4, Logging 6.3, Logging 6.2, Logging 6.1, Logging 6.0

Issue:

https://issues.redhat.com/browse/OBSDOCS-2467

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

Documentation Link:
https://docs.redhat.com/en/documentation/red_hat_openshift_logging/6.3/html/installing_logging/installing-logging#installing-loki-operator-web-console_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
~~~
@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Nov 12, 2025
@ocpdocs-previewbot
Copy link

🤖 Wed Nov 12 19:09:45 - Prow CI generated the docs preview:

https://102404--ocpdocs-pr.netlify.app/openshift-logging/latest/installing/installing-logging.html

@openshift-ci
Copy link

openshift-ci bot commented Nov 12, 2025

@prithvipatil97: 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.

@prithvipatil97
Copy link
Contributor Author

Hello Team,
I need QE approval for this change.
This change is similar to 102311 (Installing the Loki Operator by using the CLI) , but this PR is specifically for the Installing Loki Operator by using the web console method.

All checks have passed, and I have reviewed the PR with the peer review checklist.

@anpingli , @QiaolingTang , it would be really helpful if someone could please take a look and provide QE approval for this change.

Thanks in advance.

@anpingli
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 13, 2025
@prithvipatil97
Copy link
Contributor Author

Hello Anping Li,
Thank you very much for providing the QE approval for this change.

Regards,
Prithviraj Patil

@prithvipatil97
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Nov 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm Indicates that a PR is ready to be merged. merge-review-needed Signifies that the merge review team needs to review this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants