[HELM] Kyuubi server should bind Pod IP by default

[pan3793]

Code of Conduct

• I agree to follow this project's Code of Conduct

Search before asking

• I have searched in the issues and found no similar issues.

What would you like to be improved?

Currently, the Helm charts explicitly set Kyuubi server binding to localhost, and if user enable HA in the meanwhile, Kyuubi server will register itself to ZK, and that causes the registered address is localhost:<thrift_port>.

kyuubi.frontend.bind.host=localhost

How should we improve?

Is it possible to dynamically apply the POD IP on launching POD?

kyuubi.frontend.bind.host=<POD_IP>

Otherwise, we can simply remove kyuubi.frontend.bind.host in the template, when absent, Kyuubi server will find the first non-localhost host/ip to bind.

Are you willing to submit PR?

• Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
• No. I cannot submit a PR at this time.

[pan3793]

cc @dnskr @hddong, WDYT?

[zwangsheng]

+1 for binding pod ip, as for solution, we can consult Expose Pod Information to Containers Through Environment Variables.

[dnskr]

Is it possible to pass Kyuubi configs through cli arguments?
For example bin/kyuubi run --conf kyuubi.frontend.bind.host=$(hostname -I).
If so, the following should work:

      containers:
        - name: kyuubi-server
          command: ["/bin/bash", "-c", "bin/kyuubi run --conf kyuubi.frontend.bind.host=$(hostname -I)"]
          ...

or as mentioned above

      containers:
        - name: kyuubi-server
          command: ["/bin/bash", "-c", "bin/kyuubi run --conf kyuubi.frontend.bind.host=$POD_IP"]
          env:
           - name: POD_IP
             valueFrom:
               fieldRef:
                 fieldPath: status.podIP

[pan3793]

Unfortunately, bin/kyuubi does not support --conf

[dnskr]

If I just remove kyuubi.frontend.bind.host=localhost from ConfigMap in the chart, than pod hostnames are used to expose jdbc connection:

2023-03-19 17:55:38.058 INFO org.apache.kyuubi.server.KyuubiTBinaryFrontendService: Starting and exposing JDBC connection at: jdbc:hive2://kyuubi-6c4f77f8cd-cssg8:10009/

It is up and running, however I cannot access kyuubi:

kubectl port-forward svc/kyuubi-thrift-binary 10009:10009 -n default
Forwarding from 127.0.0.1:10009 -> 10009
Forwarding from [::1]:10009 -> 10009
Handling connection for 10009
E0319 19:03:55.326853    1708 portforward.go:406] an error occurred forwarding 10009 -> 10009: error forwarding port 10009 to pod 17a3f3267cd036026153da1739f7769de1d4e8ba6099e6db8bbdb9e40cdb0f62, uid : exit status 1: 2023/03/19 18:03:55 socat[31603] E connect(5, AF=2 127.0.0.1:10009, 16): Connection refused
E0319 19:03:55.327812    1708 portforward.go:234] lost connection to pod

[pan3793]

Sorry, I forget to mention that kyuubi.frontend.connection.url.use.hostname=false