Skip to content

Admission webhook logs high-volume request details (including userinfo) at INFO level with no log level configuration #700

@michaelprice232

Description

@michaelprice232

Description

The admission webhook currently logs full AdmissionReview request and response details at INFO level. This includes the userinfo block from the request as well as the generated JSON patch response. In addition, there is no configurable log level to reduce verbosity in production environments.

Because the webhook is triggered on every Pod CREATE operation, this results in five INFO log entries per pod admission. In active clusters, this can generate a significant volume of logs.

Expected Behavior

The ability to reduce the log verbosity via a log level.

Steps to Reproduce

Deploy the nri-metadata-injection Helm chart from this repo into a minikube environment and then provision pods. Observe the logs in the controller pod.

Your Environment

For testing: running minikube and the above chart directly.

For Maintainers Only or Hero Triaging this bug

Suggested Priority (P1,P2,P3,P4,P5):
Suggested T-Shirt size (S, M, L, XL, Unknown):

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions