[Feature] Improving arrow flight sql with Kubernetes setup #44599

Activity

1. jonasbrami

   added

   kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.

   on Nov 26, 2024
2. jonasbrami

   changed the title [-][Feature] [/-] [+][Feature] Improving arrow flight sql in Kubernetes[/+] on Nov 26, 2024
3. jonasbrami

   changed the title [-][Feature] Improving arrow flight sql in Kubernetes[/-] [+][Feature] Improving arrow flight sql with Kubernetes setup[/+] on Nov 26, 2024
4. xinyiZzz commented on Dec 2, 2024

   

   xinyiZzz

   on Dec 2, 2024

   Last edited by xinyiZzz

   Contributor

   More actions

   Hi @jonasbrami , thanks for your suggestion.

   Are you talking about implementing a custom reverse proxy in Kubernetes?

   That's a great idea, when you're ready, you can describe how to do it, which hopefully will be a common feature.
5. jonasbrami commented on Dec 3, 2024

   

   jonasbrami

   on Dec 3, 2024

   Author

   More actions

   I was thinking about the following:

   1. Doris Operator exposes configuration of a base public hostname for the Doris backends. For example public-hostname-doris.dev.
   2. The operator would set in the be conf the public host to be something like public-hostname-doris.dev/be{I}.
   3. Then it is possible to leverage something like Traefik to route all HTTP calls to public-hostname-doris.dev/be{I} to the right internal service.

   Maybe it is more an issue to open for Doris Kubernetes operator than for Doris itself. The only requirement for Doris is to expose the public hostname config but it is already the case
6. xinyiZzz commented on Dec 5, 2024

   

   xinyiZzz

   on Dec 5, 2024

   Contributor

   More actions

   I was thinking about the following:

   1. Doris Operator exposes configuration of a base public hostname for the Doris backends. For example public-hostname-doris.dev.
   2. The operator would set in the be conf the public host to be something like public-hostname-doris.dev/be{I}.
   3. Then it is possible to leverage something like Traefik to route all HTTP calls to public-hostname-doris.dev/be{I} to the right internal service.

   Maybe it is more an issue to open for Doris Kubernetes operator than for Doris itself. The only requirement for Doris is to expose the public hostname config but it is already the case

   Sounds like a good idea, I will contact the developers of Doris Kubernetes Operator to confirm this.
7. jonasbrami commented on Dec 5, 2024

   

   jonasbrami

   on Dec 5, 2024

   Author

   More actions

   Coool! Thank you! I would be happy to try implementing this

   👍React with 👍1Reacted by Xinyi Zou

   🚀React with 🚀1Reacted by Xinyi Zou
8. hechao-ustc commented on Dec 10, 2024

   

   hechao-ustc

   on Dec 10, 2024

   Contributor

   More actions

   I was thinking about the following:

   1. Doris Operator exposes configuration of a base public hostname for the Doris backends. For example public-hostname-doris.dev.
   2. The operator would set in the be conf the public host to be something like public-hostname-doris.dev/be{I}.
   3. Then it is possible to leverage something like Traefik to route all HTTP calls to public-hostname-doris.dev/be{I} to the right internal service.

   Maybe it is more an issue to open for Doris Kubernetes operator than for Doris itself. The only requirement for Doris is to expose the public hostname config but it is already the case

   Hi, @jonasbrami, #42881 can this PR meet your 1~2 requirements. If yes, you can wait for this PR to be merged before doing the third requirement.
9. github-actions commented on Sep 12, 2025

   

   github-actionsBot

   on Sep 12, 2025 – with GitHub Actions

   Contributor

   More actions

   We're closing this issue because it hasn't been updated in a while.
   If you'd like to revive this issue, please reopen it and feel free a maintainer to remove the Stale tag!
10. github-actions

    added

    Stale

    on Sep 12, 2025
11. github-actions

    closed this as completedon Sep 13, 2025