Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

http2: no cached connection was available #467

Closed
Drupi opened this issue Nov 29, 2019 · 3 comments · Fixed by #474
Closed

http2: no cached connection was available #467

Drupi opened this issue Nov 29, 2019 · 3 comments · Fixed by #474
Labels
Milestone

Comments

@Drupi
Copy link

Drupi commented Nov 29, 2019

Hello,
I'm using the haproxy-ingress on K8S and from time to time the haproxy-ingress get an problem with connection to api-server which stuck our ingress controller.
sample logs:

E1129 04:59:40.748091       7 reflector.go:205] pkg/mod/k8s.io/client-go@v5.0.0+incompatible/tools/cache/reflector.go:99: Failed to list *v1.Endpoints: Get https://172.20.0.1:443/api/v1/endpoints?resourceVersion=0: http2: no cached connection was available
E1129 04:59:40.749053       7 reflector.go:205] pkg/mod/k8s.io/client-go@v5.0.0+incompatible/tools/cache/reflector.go:99: Failed to list *v1.ConfigMap: Get https://172.20.0.1:443/api/v1/configmaps?resourceVersion=0: http2: no cached connection was available
E1129 04:59:40.750024       7 reflector.go:205] pkg/mod/k8s.io/client-go@v5.0.0+incompatible/tools/cache/reflector.go:99: Failed to list *v1.Secret: Get https://172.20.0.1:443/api/v1/secrets?resourceVersion=0: http2: no cached connection was available
E1129 04:59:40.751076       7 reflector.go:205] pkg/mod/k8s.io/client-go@v5.0.0+incompatible/tools/cache/reflector.go:99: Failed to list *v1.Node: Get https://172.20.0.1:443/api/v1/nodes?resourceVersion=0: http2: no cached connection was available
E1129 04:59:40.752138       7 reflector.go:205] pkg/mod/k8s.io/client-go@v5.0.0+incompatible/tools/cache/reflector.go:99: Failed to list *v1.Service: Get https://172.20.0.1:443/api/v1/services?resourceVersion=0: http2: no cached connection was available
E1129 04:59:40.753228       7 reflector.go:205] pkg/mod/k8s.io/client-go@v5.0.0+incompatible/tools/cache/reflector.go:99: Failed to list *v1.Pod: Get https://172.20.0.1:443/api/v1/pods?resourceVersion=0: http2: no cached connection was available
E1129 04:59:40.754297       7 reflector.go:205] pkg/mod/k8s.io/client-go@v5.0.0+incompatible/tools/cache/reflector.go:99: Failed to list *v1beta1.Ingress: Get https://172.20.0.1:443/apis/extensions/v1beta1/ingresses?resourceVersion=0: http2: no cached connection was available
E1129 04:59:41.748319       7 reflector.go:205] pkg/mod/k8s.io/client-go@v5.0.0+incompatible/tools/cache/reflector.go:99: Failed to list *v1.Endpoints: Get https://172.20.0.1:443/api/v1/endpoints?resourceVersion=0: http2: no cached connection was available

Do you have some expierience how to fix it ?

We are on image: quay.io/jcmoraisjr/haproxy-ingress:v0.9-snapshot.2

@jcmoraisjr
Copy link
Owner

Hi, thanks for reporting. I can confirm this behaviour on apiservers with high availability due to go upgrade without upgrading k8s client. Please check if you can reproduce this with snapshot.1. Btw you can copy vendor from release-0.8 and build v0.9 with go1.9.2 which should fix this issue as well.

I'm closing some last-minute v0.8 issues and will take care of this update. Tagging a new snapshot in a week or so.

@jcmoraisjr jcmoraisjr added this to the v0.9 milestone Nov 29, 2019
@Drupi
Copy link
Author

Drupi commented Nov 30, 2019

@jcmoraisjr - Thank you for you response - i think we will wait till the official release ;)
Will try to reproduce it on snapshot.1

@jcmoraisjr
Copy link
Owner

Hi, please let me know if you can reproduce this issue with v0.9-snapshot.3. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants