Blaine Gardner 7586cea049 core: create TRACE_INSECURE log level ...

Create a new log level for Rook that is hidden from users. This is the
most verbose log level, and it is the level developers would like to use
to get debug logs that are important for debugging but that could leak
senstivie information like credentials in production use.

If a user sets their debug level to "TRACE", they will merely get
"DEBUG" level logs. Only if they set "TRACE_INSECURE" will they get
trace logs, and those are likely to include insecure information. Rook
tries very hard not to leak sensitive information in logs even with
verbose "DEBUG" logs.

Resolves #8778

Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>

2021-10-01 12:09:19 -06:00

..

dependents

ceph: block delete object store when buckets exist

2021-06-29 14:31:39 -06:00

display

ceph: remove obsolete ipv4 command line flags

2020-03-19 07:49:53 -06:00

exec

rgw: update period if period does not exist

2021-09-28 14:17:04 -06:00

flags

ceph: refactor operator initialization sequence

2021-09-17 16:57:12 +02:00

sys

ceph: print the output on errors

2021-09-09 12:42:01 +02:00

error.go

ceph: implement dependencies for CephCluster

2021-06-10 10:06:10 -06:00

file.go

ceph: add ClusterID and PoolID mappings between local and peer cluster

2021-08-31 20:08:56 +05:30

logging_test.go

core: create TRACE_INSECURE log level

2021-10-01 12:09:19 -06:00

logging.go

core: create TRACE_INSECURE log level

2021-10-01 12:09:19 -06:00

retry.go

ceph: do not stack trace on error

2021-08-03 11:48:54 +02:00