[GitHub] [apisix] jeffguorg edited a comment on issue #2533: request help: failed to set server peer [some-k8s-svc.default.svc.cluster.local:5202] err: no host allowed

2020-10-29 Thread GitBox 


jeffguorg edited a comment on issue #2533:
URL: https://github.com/apache/apisix/issues/2533#issuecomment-719119397


   setting resolv.conf does not fix this problem.
   
   ```bash
   guochao@chao-20kna04gcd ~ % curl http:/// 
   
   502 Bad Gateway
   
   502 Bad Gateway
   openresty
   
   
   guochao@chao-20kna04gcd ~ % kubectl --namespace apisix exec -it apisix-msfhx 
-- cat /etc/resolv.conf
   nameserver 172.21.0.10
   ```
   
   i'm gonna give 2.0 a try 



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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] jeffguorg edited a comment on issue #2533: request help: failed to set server peer [some-k8s-svc.default.svc.cluster.local:5202] err: no host allowed

2020-10-29 Thread GitBox 


jeffguorg edited a comment on issue #2533:
URL: https://github.com/apache/apisix/issues/2533#issuecomment-719115231


   @membphis 
   
   yes, i started to use apisix just a few day ago before 2.0 is released.
   
   so this is already fix in 2.0, right? is it possible to backport it to 1.5? 
i'm worried that 2.x branch is not stable enough for production
   
   edit: Found that resolv.conf can be overwrite manually after set dnsPolicy 
to None: 
https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-policy.
 i would try this possible workaround first



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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [apisix] jeffguorg edited a comment on issue #2533: request help: failed to set server peer [some-k8s-svc.default.svc.cluster.local:5202] err: no host allowed

2020-10-29 Thread GitBox 


jeffguorg edited a comment on issue #2533:
URL: https://github.com/apache/apisix/issues/2533#issuecomment-719115231


   @membphis 
   
   yes, i started to use apisix just a few day ago before 2.0 is released.
   
   so this is already fix in 2.0, right? is it possible to backport it to 1.5? 
i'm worried that 2.x branch is not stable enough for production
   
   edit: Found that resolv.conf can be overwrite manually after set dnsPolicy: 
https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-policy.
 i would try this workaround first



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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org