Created new cluster in GKE and see in logs error:
"ERROR: logging before flag.Parse: E0907 16:33:58.813216 1 nanny_lib.go:128] Get https://10.0.0.1:443/api/v1/nodes?resourceVersion=0: http2: no cached connection was available "
{
textPayload: "ERROR: logging before flag.Parse: E0907 16:33:58.813216 1 nanny_lib.go:128] Get https://10.0.0.1:443/api/v1/nodes?resourceVersion=0: http2: no cached connection was available"
insertId: "zzz"
resource: {
type: "k8s_container"
labels: {
project_id: "zzz"
namespace_name: "kube-system"
container_name: "metrics-server-nanny"
pod_name: "metrics-server-v0.3.6-7b7d6c7576-jksst"
cluster_name: "zzz"
location: "zzz"
}
}
timestamp: "2020-09-07T16:33:58.813411604Z"
severity: "ERROR"
labels: {
gke.googleapis.com/log_type: "system"
k8s-pod/version: "v0.3.6"
k8s-pod/k8s-app: "metrics-server"
k8s-pod/pod-template-hash: "7b7d6c7576"
}
logName: "projects/zzz/logs/stderr"
receiveTimestamp: "2020-09-07T16:34:05.273766386Z"
}
I try to find a solution on how to fix this error.
Master version: 1.16.13-gke.1
Cloud Operations for GKE: System and workload logging and monitoring
I've test in my account with versions:
1.16.13-gke.1
,1.16.13-gke.400
and1.17.9-gke1503
and got a similar error, but not the same:Since I haven't deployed anything in the cluster, it seems to me some issue in System and workload logging and monitoring plugin enabled by default in GKE.
My sugestion is open a ticket public issue in GCP Issue tracker since the containers are managed by GKE.