xianshun163 opened a new issue, #1269:
URL: https://github.com/apache/apisix-ingress-controller/issues/1269

   ### Issue description
   
   1、I have a  service , it have a port for  http,  and  other port for grpc
   2、when  I config  the apisixupstream  and  apisixroute, And then  I go to 
the  apisix dashboard  to check  the config ,
         the  result is unstable
   3、some times the upstream of the  grpc route in  the dashboard is grpc, and 
sometimes it is http.
   
   here is my config 
   ```
    kubectl describe apisixupstreams  xstesta    -n test-devops
   Name:         xstesta
   Namespace:    test-devops
   Labels:       <none>
   Annotations:  <none>
   API Version:  apisix.apache.org/v2beta3
   Kind:         ApisixUpstream
   Metadata:
     Creation Timestamp:  2022-08-25T01:03:05Z
     Generation:          5
     Resource Version:    340777668
     Self Link:           
/apis/apisix.apache.org/v2beta3/namespaces/test-devops/apisixupstreams/xstesta
     UID:                 519e9580-9eeb-413a-b7f8-263f49982fe6
   Spec:
     Port Level Settings:
       Port:    2080
       Scheme:  grpc
       Port:    9001
       Scheme:  http
     Timeout:
       Connect:  4s
       Read:     4s
       Send:     4s
   Events:
     Type    Reason           Age                   From           Message
     ----    ------           ----                  ----           -------
     Normal  ResourcesSynced  9m31s (x5 over 131m)  ApisixIngress  
ApisixIngress synced successfully
   
   
   
   kubectl describe apisixroute xstesta-2080 -n test-devops
   Name:         xstesta-2080
   Namespace:    test-devops
   Labels:       <none>
   Annotations:  <none>
   API Version:  apisix.apache.org/v2beta3
   Kind:         ApisixRoute
   Metadata:
     Creation Timestamp:  2022-08-25T03:16:57Z
     Generation:          1
     Resource Version:    340783586
     Self Link:           
/apis/apisix.apache.org/v2beta3/namespaces/test-devops/apisixroutes/xstesta-2080
     UID:                 757bd0e6-ed91-46fe-800b-aa5c69b79f85
   Spec:
     Http:
       Backends:
         Service Name:  xstesta
         Service Port:  2080
       Match:
         Paths:
           /xstestagrpc/*
       Name:  rule1
       Plugins:
       Priority:  0
   Status:
     Conditions:
       Message:              Sync Successfully
       Observed Generation:  1
       Reason:               ResourcesSynced
       Status:               True
       Type:                 ResourcesAvailable
   Events:
     Type    Reason           Age                From           Message
     ----    ------           ----               ----           -------
     Normal  ResourcesSynced  47s (x2 over 47s)  ApisixIngress  ApisixIngress 
synced successfully
   
   ````
   
![image](https://user-images.githubusercontent.com/32457473/186567814-c4aa0a8a-50e3-479f-8cf5-bda5c158cedc.png)
   
   
![image](https://user-images.githubusercontent.com/32457473/186569863-6ff9bb66-b5c4-4f8d-bff2-f80e9c70c098.png)
   
   
   
   ### Environment
   
   - your apisix-ingress-controller version (output of 
apisix-ingress-controller version --long):1.4
   - your Kubernetes cluster version (output of kubectl version):  test env 
1.17.9,   prod env 1.21
   - if you run apisix-ingress-controller in Bare-metal environment, also show 
your OS version (uname -a):
   
   
   ### Minimal test code / Steps to reproduce
   
   1、deploy a service  with  2 port
   2、config  apisixupstream 
   3、config apisixroute for http
   4、config apisixroute for grpc
   goto the  apisix dashboard  to  see the upstream  .
   
   you can do more  test  by  delete the apisixroute of grpc,  and create it 
again.
   
   
   
   ### Actual result
   
   in  the  dashboard   the  grpc route‘s upstream  have  the schema  grpc。
   
   
   ### Error log
   
   in  the  dashboard   the  grpc route‘s upstream  have  the schema  http  
some  times , 
   it is Unstable 
   
   
   ### Expected result
   
   _No response_


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