You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2020/09/27 06:22:49 UTC

[GitHub] [rocketmq-operator] yhz1985 opened a new issue #62: My app that outside the k8s's cluster can't interview the rockermq that be dployed in k8s

yhz1985 opened a new issue #62:
URL: https://github.com/apache/rocketmq-operator/issues/62


   I deploy the nameserver's service for Nodeport,but My app that outside the k8s's cluster  can't interview the rockermq that be dployed in k8s.
   And I look at the logs ,it tell me the app interview  the broker pod's ip。 Why it is?
   
    
   ![image](https://user-images.githubusercontent.com/19431363/94357603-e2015a80-00cc-11eb-8af3-d454d292861e.png)
   


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

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



[GitHub] [rocketmq-operator] linjiemiao edited a comment on issue #62: My app that outside the k8s's cluster can't interview the rockermq that be dployed in k8s

Posted by GitBox <gi...@apache.org>.
linjiemiao edited a comment on issue #62:
URL: https://github.com/apache/rocketmq-operator/issues/62#issuecomment-699610528


   This is because the ip of the broker is the intranet ip of k8s, and the ip registered by the broker with the nameserver is also the intranet ip. Therefore, you cannot directly access the intranet ip of the broker outside the cluster. If your development environment needs to be debugged, you can use docker-compose to deploy a cluster. Then you can use rocketmq-operator to deploy in the test environment and production environment.
   
   
   rocketmq-docker-compose: https://github.com/silotrd/rocketmq-docker-compose
   
   you can change image


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

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



[GitHub] [rocketmq-operator] RongtongJin closed issue #62: My app that outside the k8s's cluster can't interview the rockermq that be dployed in k8s

Posted by GitBox <gi...@apache.org>.
RongtongJin closed issue #62:
URL: https://github.com/apache/rocketmq-operator/issues/62


   


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

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



[GitHub] [rocketmq-operator] linjiemiao edited a comment on issue #62: My app that outside the k8s's cluster can't interview the rockermq that be dployed in k8s

Posted by GitBox <gi...@apache.org>.
linjiemiao edited a comment on issue #62:
URL: https://github.com/apache/rocketmq-operator/issues/62#issuecomment-699610528


   This is because the ip of the broker is the intranet ip of k8s, and the ip registered by the broker with the nameserver is also the intranet ip. Therefore, you cannot directly access the intranet ip of the broker outside the cluster. If your development environment needs to be debugged, you can use docker-compose to deploy a cluster. Then you can use rocketmq-operator to deploy in the test environment and production environment.
   
   
   rocketmq-docker-compose: https://github.com/silotrd/rocketmq-docker-compose
   
   you can change image
   
   
   In another case, you need to make sure that the ip assigned by your k8s network plug-in for pod can be accessed by your company's development network.


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

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



[GitHub] [rocketmq-operator] linjiemiao commented on issue #62: My app that outside the k8s's cluster can't interview the rockermq that be dployed in k8s

Posted by GitBox <gi...@apache.org>.
linjiemiao commented on issue #62:
URL: https://github.com/apache/rocketmq-operator/issues/62#issuecomment-699610528


   This is because the ip of the broker is the intranet ip of k8s, and the ip registered by the broker with the nameserver is also the intranet ip. Therefore, you cannot directly access the intranet ip of the broker outside the cluster. If your development environment needs to be debugged, you can use docker-compose to deploy a cluster. Then you can use rocketmq-operator to deploy in the test environment and production environment.
   
   
   rocketmq-docker-compose: https://github.com/silotrd/rocketmq-docker-compose


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

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