[ENHANCEMENT] Ingress for Operate and Tasklist actuator endpoint

[Parth-Shah-99]

Describe the use case:

As Operate and Tasklist actuator endpoints are available on a different port 9600 then the web app which is on 80, the actuator endpoint are NOT accessible directly via operate context path.

For example, if the context path for Operate is set as /operate, then the ingress will be deployed with service name as camunda-platform-operate-service with port as 80. However, on this context path /operate, actuator won't work because the actuator endpoint is available on a different port 9600, which is not exposed via ingress.

Describe the enhancement/feature:

Add a section in Helm Chart under global ingress for Operate and Tasklist to add the ingress/context path for actuator endpoints as well.

Desired outcome and acceptance tests:

After installing Helm Chart, the actuator endpoints should be available at context path /operate/actuator.

[hisImminence]

Hi @Parth-Shah-99 thanks for your request - the actuator endpoints should not be publicly available as they are used for administrative purposes, e.g. exposing the purge or backup API (we do not recommend to expose them publicly).

If you you want to expose them, you can your own ingress object exposing these ports (as mentioned - we do not recommend that).

Closing as won't fix.