You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/01/27 09:41:12 UTC

[GitHub] [apisix-helm-chart] labaq opened a new issue #224: missing TCP port after set stream tcp port on values file

labaq opened a new issue #224:
URL: https://github.com/apache/apisix-helm-chart/issues/224


   using stream on helm values, but gateway service not open stream port 9100
   ```
   gateway:
     type: NodePort
     # If you want to keep the client source IP, you can set this to Local.
     # ref: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
     externalTrafficPolicy: Cluster
     # type: LoadBalancer
     # annotations:
     #   service.beta.kubernetes.io/aws-load-balancer-type: nlb
     externalIPs: []
     http:
       enabled: true
       servicePort: 80
       containerPort: 9080
     tls:
       enabled: false
       servicePort: 443
       containerPort: 9443
       existingCASecret: ""
       certCAFilename: ""
       http2:
         enabled: true
     stream:  # L4 proxy (TCP/UDP)
       enabled: true
       only: false
       tcp:
       - 9100
   ```
   ```
   NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
   apisix-admin           ClusterIP   10.97.177.133   <none>        9180/TCP            33m
   apisix-etcd            ClusterIP   10.104.172.79   <none>        2379/TCP,2380/TCP   33m
   apisix-etcd-headless   ClusterIP   None            <none>        2379/TCP,2380/TCP   33m
   apisix-gateway         NodePort    10.106.133.61   <none>        80:32011/TCP        33m
   ```
   part of pod spec
   ```
   spec:
     containers:
     - image: apache/apisix:2.10.0-alpine
       imagePullPolicy: IfNotPresent
       lifecycle:
         preStop:
           exec:
             command:
             - /bin/sh
             - -c
             - sleep 30
       name: apisix
       ports:
       - containerPort: 9080
         name: http
         protocol: TCP
       - containerPort: 9443
         name: tls
         protocol: TCP
       - containerPort: 9180
         name: admin
         protocol: TCP
       readinessProbe:
         failureThreshold: 6
         initialDelaySeconds: 10
         periodSeconds: 10
         successThreshold: 1
         tcpSocket:
           port: 9080
         timeoutSeconds: 1
       resources: {}
   ```
   
   my question is that need open stream port on service and pod is that right?
   or do i missing something to set
   
   i want to proxy tcp service like redis or mysql
   


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [apisix-helm-chart] labaq commented on issue #224: missing TCP port after set stream tcp port on values file

Posted by GitBox <gi...@apache.org>.
labaq commented on issue #224:
URL: https://github.com/apache/apisix-helm-chart/issues/224#issuecomment-1031098801


   Thanks, this is my expected


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [apisix-helm-chart] tokers commented on issue #224: missing TCP port after set stream tcp port on values file

Posted by GitBox <gi...@apache.org>.
tokers commented on issue #224:
URL: https://github.com/apache/apisix-helm-chart/issues/224#issuecomment-1023056410


   @labaq The `ports` field in the Pod definition is just used to tell readers or other controllers that this pod will expose these ports, but it won't affect the real behaviors of the process inside the pod, ports missing from the field can still be listened.
   
   But I think it would be better to advertise all ports in the `ports` field, would you like to submit a PR to enhance this? Thanks!


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [apisix-helm-chart] Gallardot commented on issue #224: missing TCP port after set stream tcp port on values file

Posted by GitBox <gi...@apache.org>.
Gallardot commented on issue #224:
URL: https://github.com/apache/apisix-helm-chart/issues/224#issuecomment-1023990318


   > @labaq The `ports` field in the Pod definition is just used to tell readers or other controllers that this pod will expose these ports, but it won't affect the real behaviors of the process inside the pod, ports missing from the field can still be listened.
   > 
   > But I think it would be better to advertise all ports in the `ports` field, would you like to submit a PR to enhance this? Thanks!
   
   @tokers 
   
   I think the service of apisix-gateway should expose the `stream proxy tcp/udp port` on `spec.ports`.  Otherwise, these ports cannot be accessed through the service. I will try to fix it.
   


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [apisix-helm-chart] tokers commented on issue #224: missing TCP port after set stream tcp port on values file

Posted by GitBox <gi...@apache.org>.
tokers commented on issue #224:
URL: https://github.com/apache/apisix-helm-chart/issues/224#issuecomment-1031337436


   > > @labaq The `ports` field in the Pod definition is just used to tell readers or other controllers that this pod will expose these ports, but it won't affect the real behaviors of the process inside the pod, ports missing from the field can still be listened.
   > > But I think it would be better to advertise all ports in the `ports` field, would you like to submit a PR to enhance this? Thanks!
   > 
   > @tokers
   > 
   > I think the service of apisix-gateway should expose the `stream proxy tcp/udp port` on `spec.ports`. Otherwise, these ports cannot be accessed through the service. I will try to fix it.
   
   Yes, that's true for `Service`.


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [apisix-helm-chart] labaq closed issue #224: missing TCP port after set stream tcp port on values file

Posted by GitBox <gi...@apache.org>.
labaq closed issue #224:
URL: https://github.com/apache/apisix-helm-chart/issues/224


   


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org