tokers commented on issue #730:
URL: 
https://github.com/apache/apisix-ingress-controller/issues/730#issuecomment-956074839


   > HI: I installed apisix-ingress using documentation, but it shows when 
viewing apisixRoute ApisixIngress synchronization failed, error: service “” not 
found
   > 
   > version: apache/apisix-ingress-controller:1.3.0 
![image]([https://user-images.githubusercontent.com/28882514/139646526-0dd07b33-0b3f-43ab-a8ac-1189ef98ec36.png)](https://user-images.githubusercontent.com/28882514/139646526-0dd07b33-0b3f-43ab-a8ac-1189ef98ec36.png%EF%BC%89)
 
![image]([https://user-images.githubusercontent.com/28882514/139646200-2b15f666-3830-445b-ac9c-c6131878c2c1.png)](https://user-images.githubusercontent.com/28882514/139646200-2b15f666-3830-445b-ac9c-c6131878c2c1.png%EF%BC%89)
 
![image]([https://user-images.githubusercontent.com/28882514/139646352-9fc15e1e-2e74-4152-9c2e-f9207afa2412.png)](https://user-images.githubusercontent.com/28882514/139646352-9fc15e1e-2e74-4152-9c2e-f9207afa2412.png%EF%BC%89)
 kubectl get svc -A NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE 
default httpbin ClusterIP 192.168.138.131 80/TCP 149m svc exists
   > 
   > # httpbin-route.yaml
   > apiVersion: apisix.apache.org/v2beta1 kind: ApisixRoute metadata: name: 
httpserver-route spec: http:
   > 
   > * name: rule1
   >   match:
   >   hosts:
   >   
   >   * local.httpbin.org
   >     paths:
   >   * /*
   >     backend:
   >     serviceName: "httpbin"
   >     servicePort: 80
   > 
   > THANKS
   
   What's the exact apisix route version that the apisix-ingress-controller 
watching? See 
[here](https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix-ingress-controller/templates/configmap.yaml#L36)
 to learn the details.


-- 
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