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


   @tao12345666333 ,   my  crd  yaml config is like below , I define 
ApisixUpstream and ApisixRoute, is that anything error for my config file?     
with the config, the apisix  work   all right, but  except  the err log below 
print always. 
   `
   2022-03-04T15:15:13+08:00       error   ingress/apisix_upstream.go:130  
failed to get service test-env/xss: service "xss" not found
   2022-03-04T15:15:13+08:00       warn    ingress/apisix_upstream.go:210  sync 
ApisixUpstream failed, will retry  {"object": 
{"Type":1,"Object":"test-env/xss","Tombstone":null}, "error": "service \"xss\" 
not found"}
   2022-03-04T15:15:13+08:00       error   ingress/apisix_upstream.go:130  
failed to get service test-env/xss2: service "xss2" not found
   2022-03-04T15:15:13+08:00       warn    ingress/apisix_upstream.go:210  sync 
ApisixUpstream failed, will retry  {"object": 
{"Type":1,"Object":"test-env/xss2","Tombstone":null}, "error": "service 
\"xss2\" not found"}
   `
   
   `
   ---
   apiVersion: apisix.apache.org/v2beta3
   kind: ApisixUpstream
   metadata:
     name: xss
   spec:
     timeout:
       connect: 3s
       read: 5s
       send: 5s
   
   ---
   apiVersion: apisix.apache.org/v2beta3
   kind: ApisixRoute
   metadata:
     name: xss
   spec:
     http:
       - name: rule1
         match:
           paths:
             - /testenv/xss/*
         backends:
           - serviceName: xssservice-svc
             servicePort: 8319
         plugins:
           - name: proxy-rewrite
             enable: true
             config:
               regex_uri:
                 - "^/testenv/xss/*"
                 - "/xs/${1}"
           - name: prometheus
   `
   
   
   


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