xianshun163 commented on issue #851:
URL: 
https://github.com/apache/apisix-ingress-controller/issues/851#issuecomment-1050720874


   @tao12345666333  I have update the version to 1.4 
   that is a err log like this :
   2022-02-25T18:11:17+08:00       error   apisix/upstream.go:156  failed to 
create upstream: Put 
"http://apisix-gw-lb.default.svc.cluster.local:9080/apisix/admin/upstreams/db067616":
 context deadline exceeded (Client.Timeout exceeded while awaiting headers)
   2022-02-25T18:11:19+08:00       error   apisix/upstream.go:76   failed to 
get upstream from APISIX      {"name": "default_xsapp-service_80", "url": 
"http://apisix-gw-lb.default.svc.cluster.local:9080/apisix/admin/upstreams/db067616";,
 "cluster": "default", "error": "Get 
\"http://apisix-gw-lb.default.svc.cluster.local:9080/apisix/admin/upstreams/db067616\":
 context deadline exceeded (Client.Timeout exceeded while awaiting headers)"}
   2022-02-25T18:11:19+08:00       error   ingress/apisix_upstream.go:151  
failed to get upstream default_xsapp-service_80: Get 
"http://apisix-gw-lb.default.svc.cluster.local:9080/apisix/admin/upstreams/db067616":
 context deadline exceeded (Client.Timeout exceeded while awaiting headers)
   [GIN] 2022/02/25 - 18:11:19 | 200 |     118.307µs |    172.16.11.15 | GET    
  "/healthz"
   2022-02-25T18:11:22+08:00       error   apisix/route.go:164     failed to 
create route: Put 
"http://apisix-gw-lb.default.svc.cluster.local:9080/apisix/admin/routes/8215ff3a":
 context deadline exceeded (Client.Timeout exceeded while awaiting headers)
   
   my upstream yaml file like this:
   apiVersion: apisix.apache.org/v2beta3
   kind: ApisixUpstream
   metadata:
     name: xsapp-service
   spec:
     timeout:
       connect: 1s
       read: 3s
       send: 3s
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to