yin6516008 edited a comment on issue #854:
URL: 
https://github.com/apache/apisix-ingress-controller/issues/854#issuecomment-1057746387


   I'm sorry, I won't be free debugging it recently,to start over again today I 
debug it, but I met this problem.
   
   apply
   ```yaml
   apiVersion: apisix.apache.org/v2beta3
   kind: ApisixRoute
   metadata:
     name: echo
     namespace: default
   spec:
     http:
     - name: echo
       match:
         hosts:
         - echo.jc-ai.cn
         paths:
         - /*
       plugin_config_name: openapi-auth
       backends:
         - serviceName: echo
           servicePort: 8080
   ```
   
   ```bash
   # kubectl describe  apisixroute  echo 
   Name:         echo
   Namespace:    default
   Labels:       <none>
   Annotations:  API Version:  apisix.apache.org/v2beta3
   Kind:         ApisixRoute
   Metadata:
     Creation Timestamp:  2022-03-03T06:47:27Z
     Generation:          1
     Resource Version:    29884427
     UID:                 fa77ba15-5ccf-4c54-b87d-7516f6a120e4
   Spec:
     Http:
       Backends:
         Service Name:  echo
         Service Port:  8080
       Match:
         Hosts:
           echo.jc-ai.cn
         Paths:
           /*
       Name:  echo
   Status:
     Conditions:
       Message:              Sync Successfully
       Observed Generation:  1
       Reason:               ResourcesSynced
       Status:               True
       Type:                 ResourcesAvailable
   Events:
     Type    Reason           Age                From           Message
     ----    ------           ----               ----           -------
     Normal  ResourcesSynced  11m (x2 over 11m)  ApisixIngress  ApisixIngress 
synced successfully
   ```
   Why are there no plugin_config_name field?
   
   


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