Production ready ingress setup (HAProxy) #2175
-
Hello, I am currently working on a production-ready setup for Eclipse Ditto in a Kubernetes cluster. Now I am wondering how to correctly set up the connection from outside to Ditto. In the helm-chart there is already a prepared ingress definition. There is even a complete setup of an ingress controller. In my case I already have an ingress controller (HAProxy) and therefore, the default settings in the chart for ingress don't work in the same way and need to be adapted for HAProxy. If the assumption is correct that this is only for a quick start, what is the recommendation? Should I keep ingress disabled and create my own ingress setup? If the answer to that is yes, should the existing Nginx in Ditto remain active and should I route everything through it? Greetings, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Hi Dominik, you're corrected the current approach is less then perfect and is more a working example how it would look like. Anyway, for your question -> Yes, disable it. You can use the internal nginx pod because it hosts ditto ui resources(if you're using/exposing the ui) and if not you can disable that as well. Afterwards you can expose everything with your HAProxy ingress controller(don't have any experience with it though). Best Regards, |
Beta Was this translation helpful? Give feedback.
Hi Dominik,
you're corrected the current approach is less then perfect and is more a working example how it would look like.
There's something that I wanted to do when I have more time and add it as a separate dependency:
#2056
Anyway, for your question -> Yes, disable it. You can use the internal nginx pod because it hosts ditto ui resources(if you're using/exposing the ui) and if not you can disable that as well. Afterwards you can expose everything with your HAProxy ingress controller(don't have any experience with it though).
Best Regards,
Kalin