Merge pull request #102311 from prithvipatil97/patch-93

Update LokiStack configuration with global limits for retention and managementState

Author: briandooley

modules/installing-loki-operator-cli.adoc

@@ -149,26 +149,33 @@ metadata:
   name: logging-loki # <1>
   namespace: openshift-logging # <2>
 spec:
-  size: 1x.small # <3>
+  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>" # <4>
+      effectiveDate: "<yyyy>-<mm>-<dd>" # <6>
     secret:
-      name: logging-loki-s3 # <5>
-      type: s3 # <6>
-  storageClassName: <storage_class_name> # <7>
+      name: logging-loki-s3 # <7>
+      type: s3 # <8>
+  storageClassName: <storage_class_name> # <9>
   tenants:
-    mode: openshift-logging # <8>
+    mode: openshift-logging # <10>
 ----
 <1> Use the name `logging-loki`.
 <2> You must specify `openshift-logging` as the namespace.
-<3> Specify the deployment size. Supported size options for production instances of Loki are `1x.extra-small`, `1x.small`, or `1x.medium`. Additionally, `1x.pico` is supported starting with {logging} 6.1.
-<4> For new installations this date should be set to the equivalent of "yesterday", as this will be the date from when the schema takes effect.
-<5> Specify the name of your log store secret.
-<6> Specify the corresponding storage type.
-<7> Specify the name of a storage class for temporary storage. For best performance, specify a storage class that allocates block storage. You can list the available storage classes for your cluster by using the `oc get storageclasses` command.
-<8> The `openshift-logging` mode is the default tenancy mode where a tenant is created for log types, such as audit, infrastructure, and application. This enables access control for individual users and user groups to different log streams.
+<3> Define global limits that apply to the LokiStack instance. For information about setting stream-based retention, see link:https://docs.redhat.com/en/documentation/red_hat_openshift_logging/6.3/html/configuring_logging/configuring-lokistack-storage#logging-loki-retention_configuring-the-log-store[Enabling stream-based retention with Loki]. This field does not impact the retention period for stored logs in object storage.
+<4> Retention is enabled in the cluster when this block is added to the CR.
+<5> Specify the deployment size. Supported size options for production instances of Loki are `1x.extra-small`, `1x.small`, or `1x.medium`. Additionally, `1x.pico` is supported starting with {logging} 6.1.
+<6> For new installations this date should be set to the equivalent of "yesterday", as this will be the date from when the schema takes effect.
+<7> Specify the name of your log store secret.
+<8> Specify the corresponding storage type.
+<9> Specify the name of a storage class for temporary storage. For best performance, specify a storage class that allocates block storage. You can list the available storage classes for your cluster by using the `oc get storageclasses` command.
+<10> The `openshift-logging` mode is the default tenancy mode where a tenant is created for log types, such as audit, infrastructure, and application. This enables access control for individual users and user groups to different log streams.
 
 
 . Apply the `LokiStack` CR object by running the following command: