We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We have at least one log statement, at the debug level, which can generate fields with "random" names:
cloud-on-k8s/pkg/controller/common/watches/handler.go
Lines 61 to 63 in e9681fe
This may for example produce the following log:
"current_registrations": { "my-project-1-es-referenced-secrets": { "Watcher": { "Namespace": "my-project-1", "Name": "es" }, "Watched": [ { "Namespace": "my-project-1", "Name": "watched-resource1" }, { "Namespace": "my-project-1", "Name": "watched-resource2" } ], "Name": "my-project-1-es-referenced-secrets" }, "my-project-2-es-referenced-secrets": { "Watcher": { "Namespace": "my-project-2", "Name": "es" }, "Watched": [ { "Namespace": "my-project-2", "Name": "watched-resource1" }, { "Namespace": "my-project-2", "Name": "watched-resource2" } ], "Name": "my-project-2-es-referenced-secrets" }, .... lots of other fields ...
This can lead to a "mapping explosion" situation.
The text was updated successfully, but these errors were encountered:
barkbay
Successfully merging a pull request may close this issue.
We have at least one log statement, at the debug level, which can generate fields with "random" names:
cloud-on-k8s/pkg/controller/common/watches/handler.go
Lines 61 to 63 in e9681fe
This may for example produce the following log:
This can lead to a "mapping explosion" situation.
The text was updated successfully, but these errors were encountered: