diff --git a/modules/installing-loki-operator-web-console.adoc b/modules/installing-loki-operator-web-console.adoc index 92d45a081c80..457d9acfa9ee 100644 --- a/modules/installing-loki-operator-web-console.adoc +++ b/modules/installing-loki-operator-web-console.adoc @@ -75,8 +75,8 @@ metadata: namespace: openshift-logging <2> stringData: <3> access_key_id: - access_key_secret: - bucketnames: s3-bucket-name + access_key_secret: + bucketnames: s3_bucket_name endpoint: https://s3.eu-central-1.amazonaws.com region: eu-central-1 ---- @@ -104,25 +104,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: "--
" + effectiveDate: "--
" # <6> secret: - name: logging-loki-s3 # <4> - type: s3 # <5> - storageClassName: # <6> + name: logging-loki-s3 # <7> + type: s3 # <8> + storageClassName: # <9> tenants: - mode: openshift-logging # <7> + 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> Specify the name of your log store secret. -<5> Specify the corresponding storage type. -<6> 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. -<7> 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. -- . Click *Create*.