Unable to resolve 'be domain name' for accessing the k8s cluster from outside. about doris-operator HOT 6 CLOSED

In K8s, stream load should direct use be access service. In stream load fe as 301 proxy. In fact, client direct interaction with be, but in k8s, be address not be direct accessed by client that out k8s.

from doris-operator.

In K8s, stream load should direct use be access service. In stream load fe as 301 proxy. In fact, client direct interaction with be, but in k8s, be address not be direct accessed by client that out k8s.

Is there an alternative solution, such as using 'hostNetwork,' to resolve the issue without using a service?

from doris-operator.

using hostNetWork is not a good choice. Kubernetes does not recommend hostnetwork mode. hostNetwork is not universal.
From use:
if using hostNetwork, the IP will change when the pod moves to node2 from node1. fe and be will not work normally. other, using hostnetwork the service will not work.

from doris-operator.

using hostNetWork is not a good choice. Kubernetes does not recommend hostnetwork mode. hostNetwork is not universal. From use: if using hostNetwork, the IP will change when the pod moves to node2 from node1. fe and be will not work normally. other, using hostnetwork the service will not work.

Are there any other recommended methods? if we want to access doris out of k8s;

from doris-operator.

for stream load, you can use access be service and service use NodePort or lb.

from doris-operator.

I closed the issue for a long time reply. if you are still confused, please reopen the issue.

from doris-operator.