Ingresses don't work out of the box for on-prem Kubernetes deployment. about activiti-cloud-full-chart HOT 4 CLOSED

I have same problem.

from activiti-cloud-full-chart.

you probably haven't installed an ingress implementation on your cluster so no Ingress resource can work

you can try with the Docker Desktop setup and see if you can reproduce your issue: https://github.com/Activiti/activiti-cloud-full-chart#running-on-docker-desktop

from activiti-cloud-full-chart.

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: nginxinc/kubernetes-ingress#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.

from activiti-cloud-full-chart.

no thanks, this is specific to that ingress implementation so definitely out of scope as it would affect any app running on kubernetes

from activiti-cloud-full-chart.