Activiti Cloud: Ingresses don't work out of the box for on-prem Kubernetes deployment.

[pablosettecase]

I'm not sure if this is the right place for Activiti cloud deployment questions, but here is mine. We're trying to evaluate Activiti Cloud for recommendation for a customer.

I've been trying to deploy the Activiti full example to an on-premise Kubernetes cluster and have found that the Ingresses don't work as expected. I've only seen support for GKE and EKS in the docs, so I wonder if I can get help on this. This is the documentation I'm following: https://activiti.gitbook.io/activiti-7-developers-guide/getting-started/getting-started-activiti-clo...

I used Helm 3 with the custom gateway value that the docs mention. After installation I am not able to view any of the services at the URL's that the Helm installation outputs, such as http // gateway-activiti.<mydomain>/modeling. All pods and services are up, and if I change the service to type NodePort it does work. From what I can tell so far the Ingresses seem to be conflicting with each other because if I modify the URL in the modeling Ingress to something different then it does seem to work.

Any help here is appreciated.

[ermedeiros]

Hi,

I've never tried it in an on-prem Kubernetes, but here are the instructions if you want to check if you have the same issue on Kubernetes running on Docker Desktop https://github.com/Activiti/activiti-cloud-full-chart#running-on-docker-desktop.

Best regards,

Elias

[mteodori]

please check the link suggested by @ermedeiros, I only have cloud experience with k8s as well but what I would try is to first test with the standard checks on the kubernetes site to rule out any issues with the chosen ingress implementation which I am guessing is the nginx one: https://kubernetes.io/docs/concepts/services-networking/ingress/#prerequisites

[pablosettecase · Accepted solution]

Thank you for the suggestions. We finally diagnosed the problem to be that multiple Ingress objects have the same host rule and were conflicting with each other. Problem is described in more detail here: https://github.com/nginxinc/kubernetes-ingress/issues/76 

Solution described in more detail here: https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/mergeable-ingress-types

We remedied this by creating a new "master" Ingress with annotation nginx.org/mergeable-ingress-type: master. Then in each Ingress with the same host rule we added the annotation of nginx.org/mergeable-ingress-type: minion.

I'd like to update the documentation to account for this for on-prem deployments.

[EddieMay]

Hi @pablosettecase 

Great that you resolved your issue & thanks for the update - really helpful to other users.

Best wishes,