[Feature Request] Allow customizing Ingress rules with pass-through variables

[FecoDoo]

It would be great if one can have the ability to fully customzing Ingress resource with https://github.com/litmuschaos/litmus-helm/tree/master/charts/litmus chart.

According to docs we need both litmusportal-server-service and litmusportal-frontend-service backends, but with the Helm chart, only the front service backend rule will be created.

[Jonsy13]

Hi @FecoDoo Can you please provide your usecase with respect to exposing litmusportal-server-service backend? We used to do it earlier but now we don't do it as it is already available via nginx conf in litmusportal-frontend-service. Just adding /api will do the same work.

Ref - https://github.com/litmuschaos/litmus/blob/master/chaoscenter/web/nginx/nginx.conf

Looks like docs are not updated accordingly, that we can update but before that wanted to understand your usecase.

[thiha-min-thant]

Hi @Jonsy13 ,

One use case for exposing the litmusportal-server-service backend is when the Execution Plane is installed with an agent in a remote environment. In such cases, custom SDKs or operators might need to interact directly with the authentication server and GraphQL server ingress endpoints.

This would allow for seamless communication and integration in scenarios where external tools or automation processes require direct access to these services.

Thanks for looking into this!

[Jonsy13]

Thanks @thiha-min-thant for providing the usecase.

So can you confirm if using litmusportal-frontend-service backend works for you or not -

• For Authentication, /auth/ should take you to authentication server.
• For GraphQL Server, /api/ should take you to graphql server.

I think it should because, Even our litmusctl & helm-agent both are using the same & they are able to do all operations.