You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the automatic collection of logs using a service such as Filebeat, it would be helpful if the logs could be output as JSON, e.g. by using a flag.
For example, you could use the JSON logging format from the Kubernetes Community Repository.
{"ts": 1580306777.04728,"v": 4,"msg": "Pod status was updated","pod":{"name": "kube-dns","namespace": "kube-system"},"status": "ready"}
The concrete use case is that the RBAC proxy runs in a pod together with a controller manager for a custom operator (created with kubebuilder).
The controller manager created with kubebuilder uses the zap logging library and it can be configured to use JSON as logging format.
It would be nice if the rbac proxy would also log using JSON logging, so that both containers in the pod use the same logging format.
This would allow Filebeat to easily collect the logs from both containers in the pod.
The text was updated successfully, but these errors were encountered:
For the automatic collection of logs using a service such as Filebeat, it would be helpful if the logs could be output as JSON, e.g. by using a flag.
For example, you could use the JSON logging format from the Kubernetes Community Repository.
The concrete use case is that the RBAC proxy runs in a pod together with a controller manager for a custom operator (created with kubebuilder).
The controller manager created with kubebuilder uses the zap logging library and it can be configured to use JSON as logging format.
It would be nice if the rbac proxy would also log using JSON logging, so that both containers in the pod use the same logging format.
This would allow Filebeat to easily collect the logs from both containers in the pod.
The text was updated successfully, but these errors were encountered: