Certificate Renewal Logs Issue #5686
saloni-2404
started this conversation in
General
Replies: 1 comment
-
I'm not sure what the actual question or issue is. I personally don't think such messages should be on the WARN level. But INFO level would be definitely better than DEBUG. There is a plan to revisit what is being logged around the CA renewals and at which level. If you want, you can also suggest what you think is important here, in an issue or with a PR. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have observed that appropriate logs are not provided in case of certificate renewal. The detailed log does exist, in the DEBUG mode, however, we would expect to see minimal amount of information as part of WARNING, for tracing purpose.
The DEBUG logs show:
2021-10-08 07:12:47 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace NS...
2021-10-08 07:12:47 DEBUG AbstractOperator:173 - Reconciliation #125(timer) Kafka(NS/test-cluster): Lock lock::NS::Kafka::test-cluster acquired
2021-10-08 07:12:47 INFO AbstractOperator:122 - Reconciliation #125(timer) Kafka(NS/test-cluster): Kafka test-cluster should be created or updated
2021-10-08 07:12:47 DEBUG KafkaAssemblyOperator:519 - Reconciliation #125(timer) Kafka(NS/test-cluster): Status is already set. No need to set initial status
2021-10-08 07:12:47 DEBUG Ca:642 - cluster-ca: CA certificate (in test-cluster-cluster-ca-cert) needs to be renewed: Within renewal period for CA certificate (expires on Sat Oct 09 07:10:50 UTC 2021)
2021-10-08 07:12:47 DEBUG Ca:508 - cluster-ca renewalType RENEW_CERT
2021-10-08 07:12:47 DEBUG Ca:921 - Renewing CA with subject=/O=io.strimzi/CN=cluster-ca v0, org={}
(Strimzi Operator version: 0.17.0)
Could you please confirm if this is the expected behaviour or if we are missing out on anything.
Beta Was this translation helpful? Give feedback.
All reactions