sum-elier commented on issue #1823:
URL: 
https://github.com/apache/apisix-ingress-controller/issues/1823#issuecomment-1572625112

   After applying your suggestion as follows (notice `ingressClassName` instead 
of the annotation)
   
   ```yaml
   apiVersion: networking.k8s.io/v1
   kind: Ingress
   metadata:
     annotations:
       k8s.apisix.apache.org/upstream-scheme: grpcs
     name: todos-ingress
     labels:
       app.kubernetes.io/name: todos
       app.kubernetes.io/component: server
       app.kubernetes.io/instance: todos-ingress-default
       app.kubernetes.io/version: "0.1.0"
   spec:
     ingressClassName: apisix
     rules:
       - http:
           paths:
             - pathType: ImplementationSpecific
               path: /
               backend:
                 service:
                   name: todos-service
                   port:
                     name: todos-app
   ```
   
   when I check the configuration of the ingress I see there's no address and 
no events, is this normal?
   
   ```shell
   > kubectl describe ingress todos-ingress
   Name:             todos-ingress
   Labels:           app.kubernetes.io/component=server
                     app.kubernetes.io/instance=todos-ingress-default
                     app.kubernetes.io/name=todos
                     app.kubernetes.io/version=0.1.0
   Namespace:        default
   Address:
   Ingress Class:    apisix
   Default backend:  <default>
   Rules:
     Host        Path  Backends
     ----        ----  --------
     *
                 /   todos-service:todos-app (10.244.2.7:47586)
   Annotations:  k8s.apisix.apache.org/upstream-scheme: grpcs
   Events:       <none>
   ```
   I suppose no because now the grpc error reads "error reading server preface: 
EOF"


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