From 901f33f7af0d0981bf41258ba59a3181b05cb73e Mon Sep 17 00:00:00 2001 From: Jon Cope Date: Wed, 21 Feb 2024 13:52:58 -0600 Subject: [PATCH] specify maxFileAge units --- enhancements/microshift/audit-log-configuration-options.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/enhancements/microshift/audit-log-configuration-options.md b/enhancements/microshift/audit-log-configuration-options.md index ef7aaf06a93..1072457124c 100644 --- a/enhancements/microshift/audit-log-configuration-options.md +++ b/enhancements/microshift/audit-log-configuration-options.md @@ -80,14 +80,14 @@ Log rotation is governed by 3 values defining file size, number of retained file - `maxFileSize` specifies maximum audit log file size. Accepted values must be a string concatenation of an integer and unit suffix with no separator character, e.g. `10GB`. Valid units are "MB", "GB", "TB". Since the kube-apiserver only accepts values defined in whole megabytes, MicroShift will need to translate this field value internally. This is trivial to implement and provides a bit of convenience to users. - `maxFiles` specifies the maximum number of rotated audit log files to retain. Once this limit is reached, the apiserver will delete log files in order from oldest to newest, until all specified limits are satisfied. - _For example_,`maxFiles: 1` results will result in only 1 rotated file being retained, provided it also is within the `maxFileAge` limit, if specified. -- `maxFileAge` specifies the maximum length of time to retain log files. Files older than this limit will be deleted. +- `maxFileAge` specifies the maximum time in days to retain log files. Files older than this limit will be deleted. ```yaml apiServer: auditLog: maxFileSize: STRING maxFiles: INT - maxFileAge: STRING + maxFileAge: INT ``` ### Topology Considerations