de9f8415d7
There are several kubernetes bugs [0,1,2] involving connection problems that seem related to the Go net/http2 library, where the stream state and connection state can get out of sync. This can manifest as a kubelet issue, where the node status gets stuck in a NotReady state, but can also happen elsewhere. In newer versions of the Go libraries some issues are fixed [3,4], but the fixes are not present in k8s 1.18. This change disables http2 in kube-apiserver and webhook-apiserver. This should be sufficient to avoid the majority of the issues, as disabling on one side of the connection is enough, and apiserver is generally either the client or the server. 0: https://github.com/kubernetes/kubernetes/issues/87615 1: https://github.com/kubernetes/kubernetes/issues/80313 2: https://github.com/kubernetes/client-go/issues/374 3: https://github.com/golang/go/issues/40423 4: https://github.com/golang/go/issues/40201 Change-Id: Id693a7201acffccbc4b3db8f4e4b96290fd50288 |
||
|---|---|---|
| .. | ||
| bin | ||
| etc | ||
| configmap-bin.yaml | ||
| configmap-certs.yaml | ||
| configmap-etc.yaml | ||
| daemonset.yaml | ||
| ingress-api.yaml | ||
| job-key-rotate.yaml | ||
| rbac.yaml | ||
| secret-apiserver.yaml | ||
| secret-ingress-tls.yaml | ||
| service-apiserver-ingress.yaml | ||
| service.yaml | ||