Skip to content

Commit 75e6039

Browse files
committed
OLS-1622: minonr changes
1 parent bc08488 commit 75e6039

File tree

1 file changed

+6
-9
lines changed

1 file changed

+6
-9
lines changed

Diff for: modules/ols-activating-token-quota-limits.adoc

+6-9
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,6 @@
77

88
Modify the `OLSConfigMap` file to activate token quota limits for the {ols-long} Service.
99

10-
:FeatureName: Token quota limits
11-
include::../snippets/technology-preview.adoc[]
12-
1310
.Prerequisites
1411

1512
* You have installed the the {ols-long} Operator.
@@ -36,8 +33,8 @@ quota_handlers:
3633
storage:
3734
host: <IP_address> <1>
3835
port: "5432"
39-
dbname: test
40-
user: tester
36+
dbname: <database_name>
37+
user: <user_name>
4138
password_path: <file_containing_database_password>
4239
ssl_mode: disable
4340
limiters:
@@ -54,11 +51,11 @@ quota_handlers:
5451
period: 300 <4>
5552
----
5653
<1> Specifies the IP address for the PostgresSQL database. The database must use port `5432`.
57-
<2> Defines the token quota limits for individual users.
58-
<3> Defines the token quota limits for clusters.
59-
<4> Defines the number of seconds the scheduler runs and then resets.
54+
<2> Specifies a token quota limit of 100,000 for each user over a period of 30 days.
55+
<3> Increases the token quota limit for the cluster by 100,000 over a period of 30 days.
56+
<4> Defines the number of seconds that the scheduler waits and then checks if the period interval is over. When the period interval is over, the scheduler stores the timestamp and resets or increases the quota limit.
6057

61-
. Apply the file so that the token limits go into effect by running the following command:
58+
. Apply the `OLSConfigMap` file so that the token limit quota takes effect by running the following command:
6259
+
6360
[source,terminal]
6461
----

0 commit comments

Comments
 (0)