Sun~shell

@travisn @jmolmo The k8s dashboard of my local cluster uses the node public IP+ node_port(123.123.123.123:30771), access is working, only ceph_dashboard will jump to the pod internal address(172.20.107.223:8443)

@jmolmo the /etc/hosts file does not have any special configuration, because I use the node's public network address+port to access it directly

@jmolmo I think we can build a ceph cluster to simulate my environment node_ip + node_port == working public_node_ip + node_port == not working(rewrite to pod internal ip + 8443)

@jmolmo I have verified the points you listed one by one, and there is no problem，I only have one node. There are two network cards on this node. One is...

@zimmerle From #2381, I don't see how to fix this problem? Now what do I need to do

@zimmerle How to solve this problem?　The impact of this problem is very serious. I hope that the government will pay close attention to the repair and repair version 3.0.4...

@zimmerle Sorry, I don't know what you mean. What I want to ask is how to solve this memory leak?

The document you provided really works. But if I change the browser I'll have normal access the web server So I think this disabling policy is only for the combination...

@mingyuan-xia 192.168.199.129:7912是可以访问的，因为我的２个手机都是连接的同一个无线路由器．我感觉我的网络没有问题，就是不知道为啥会说addr is invalid or atx-agent is not running', '192.168.199.129

@zongtanghu @shendongsd Whether rocketmq-operator support Dledger way to deployment RocketMQ cluster ?