-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Installing Loki Operator by using the web console #102404
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
base: standalone-logging-docs-main
Are you sure you want to change the base?
Installing Loki Operator by using the web console #102404
Conversation
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 ~~~
|
🤖 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 |
|
@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. |
|
Hello Team, 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. |
|
/lgtm |
|
Hello Anping Li, Regards, |
|
/label merge-review-needed |
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:
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:
Additional information: