[GitHub] [rocketmq] WSYwsy22 opened a new issue, #6268: rocketmq-proxy does not work properly in k8s nodePort mode

["WSYwsy22 (via GitHub)" <gi...@apache.org>]

WSYwsy22 opened a new issue, #6268:
URL: https://github.com/apache/rocketmq/issues/6268

   The issue tracker is used for bug reporting purposes **ONLY** whereas feature request needs to follow the [RIP process](https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal). To avoid unnecessary duplication, please check whether there is a previous issue before filing a new one.
   
   It is recommended to start a discussion thread in the [mailing lists](http://rocketmq.apache.org/about/contact/) or [github discussions](https://github.com/apache/rocketmq/discussions) in cases of discussing your deployment plan, API clarification, and other non-bug-reporting issues.
   We welcome any friendly suggestions, bug fixes, collaboration, and other improvements.
   
   Please ensure that your bug report is clear and self-contained. Otherwise, it would take additional rounds of communication, thus more time, to understand the problem itself.
   
   Generally, fixing an issue goes through the following steps:
   1. Understand the issue reported;
   1. Reproduce the unexpected behavior locally;
   1. Perform root cause analysis to identify the underlying problem;
   1. Create test cases to cover the identified problem;
   1. Work out a solution to rectify the behavior and make the newly created test cases pass;
   1. Make a pull request and go through peer review;
   
   As a result, it would be very helpful yet challenging if you could provide an isolated project reproducing your reported issue. Anyway, please ensure your issue report is informative enough for the community to pick up. At a minimum, include the following hints:
   
   **BUG REPORT**
   
   1. Please describe the issue you observed:
   
   - What did you do (The steps to reproduce)?
       1、Prepare a k8s cluster
   
       2、Deploy a rocketmq cluster in a k8s cluster, the simplest cluster mode, only one broker, one proxy, one namespace
   
       3、There is the following k8s service yaml file
   ```yaml
   apiVersion: v1
   kind: Service
   metadata:
     name: lbs-{{ .Values.proxy.name }}
   spec:
     type: NodePort
     selector:
       app: {{ .Values.proxy.name }}
     ports:
       - port: 8081
         targetPort: 8081
         nodePort: 30872
   ```
          Because the self-built k8s cluster does not have the function of automatically assigning domain names provided by cloud vendors, so I use nodePort to expose the port method
          When the nodePort port I exposed is inconsistent with the grpcServer port, rocketmq-proxy cannot return valid information to me normally
   
        4、 This problem was fixed in pr, compatible with k8s NodePort mode
   
   - What is expected to see?
        I want rocketmq-proxy to work fine in k8s NodePort
   
   - What did you see instead?
        rocketmq-proxy does not work properly in k8s NodePort mode    
   
   2. Please tell us about your environment:
        k8s    1.23
        rocketmq  5.1.0
   
   3. Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):
        
   


-- 
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: commits-unsubscribe@rocketmq.apache.org.apache.org

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

[GitHub] [rocketmq] xdkxlk closed issue #6268: rocketmq-proxy does not work properly in k8s nodePort mode

["xdkxlk (via GitHub)" <gi...@apache.org>]

xdkxlk closed issue #6268: rocketmq-proxy does not work properly in k8s nodePort mode
URL: https://github.com/apache/rocketmq/issues/6268


-- 
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: commits-unsubscribe@rocketmq.apache.org

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