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
I looked into this and found that those audit logs are normal and not harmful. I think we can close this issue.
At first, those logs are generated here and intended to record a long running request (i.e. watch API). I’m not a person in GKE team, so the only thing I can do is guessing from the sample Audit policy here. The default level is set to Metadata, and the kube-apiserver log request metadata without request and response body. As you know, the Argo CD application controller is calling watch API for available resources, so Connection closed early messages are logged. I’m not sure why those logs are not written when using argocd-manager service account in kube-system namespace, but I doubt that the requests authenticating with GCP service account are targeted.
I found other controller in a similar situation. The following is the audit logs for watch API called by GKE internal controllers with GCP internal service account:
As per, 9786
cc @toVersus
The text was updated successfully, but these errors were encountered: