This message was deleted.
# general
a
This message was deleted.
c
This does not happen on my MAC or in Ubuntu 18. But does on Ubuntu 20.
t
what kubernetes version is it?
and what Rancher version?
c
rancher 2.6.1, k8s EKS 1.20
I just built a brand new deployment machine using ubuntu 18. And encountered the same problem.
Ran:
rancher kubectl rollout status -w deployment acmepa -n acmepa
and got this response:
Copy code
deployment "acmepa" successfully rolled out
E0818 17:54:51.211673    8228 reflector.go:383] <http://k8s.io/client-go/tools/watch/informerwatcher.go:146|k8s.io/client-go/tools/watch/informerwatcher.go:146>: Failed to watch *unstructured.Unstructured: Get <https://rch2.panosoft.com/k8s/clusters/c-mjkrt/apis/apps/v1/namespaces/acmepa/deployments?allowWatchBookmarks=true&fieldSelector=metadata.name%3Dacmepa&resourceVersion=134547883&timeoutSeconds=461&watch=true>: unexpected EOF
similar to others that posted in that tread I linked to earlier.
t
In the comments on that issue, they said it worked when http2 was disabled in the ingress - https://github.com/rancher/rancher/issues/21324#issuecomment-952457417 does that have any effect?
c
I will check that. Not sure if I am using nginx lb or not.
hmmm that fix assumes that I have a configmap called
Copy code
nginx-configuration
which I do not.
This was the command that I used to install and create the ingress:
Copy code
helm repo add ingress-nginx <https://kubernetes.github.io/ingress-nginx>
helm repo update
helm upgrade --install \
  ingress-nginx ingress-nginx/ingress-nginx \
  --namespace ingress-nginx \
  --set controller.service.type=LoadBalancer \
  --version 3.12.0 \
  --create-namespace
The result was and classic ELB.
weird thing is that was created 300 days ago. But this problem only recently started happening.
t
Since it only recently started happening, did anything else change recently?
A bug with proxied kubectl commands hanging was fixed in 2.6.6 https://github.com/rancher/rancher/issues/37707, so I would be interested to know if this bug is also reproducible in 2.6.6.
c
is 2.6.6 considered stable yet?
So I disabled http/2 on the server load balancer and that resolved the issue.
t
2.6.7 is the latest stable version