litmus
litmus copied to clipboard
Run Litmus behind reverse-proxy
Question
Hi,
I would like to deploy Litmus in one of my EKS clusters,
All of my infra applications run's on the same domain but different path ( www.example.com/<<app>>) by using nginx-ingress controller
When trying to load Litmus, the frontend app is trying to get static content from www.example.com/ and i would like to know if there is a way to set BaseURL to Litmus to load the client with /litmus . (something like this https://argoproj.github.io/argo-workflows/argo-server/#base-href)

Hi @dorroddorrod, currently, it is possible to run the frontend in a "/litmuschaos" path. You just need to replace frontend's docker image with litmuschaos/litmusportal-frontend-path-litmuschaos:<version>
Please note, only "/litmuschaos" path is possible with this image.
Cool ! thanks for the quick response :)
@rajdas98 After changing the default image to litmuschaos/litmusportal-frontend-path-litmuschaos:<version>
I'm getting the following error from the subscriber pod
***@IL-C02FF8LHMD6P ~ % kubectl logs -f subscriber-6cb89f4d97-r2vcl -n litmus
time="2021-11-04T12:08:37Z" level=info msg="Go Version: go1.16.9"
time="2021-11-04T12:08:37Z" level=info msg="Go OS/Arch: linux/amd64"
time="2021-11-04T12:08:37Z" level=info msg="all deployments up"
time="2021-11-04T12:08:37Z" level=info msg="all components live...starting up subscriber"
time="2021-11-04T12:08:37Z" level=fatal msg="failed to parse cluster confirm data" data="<html>\r\n<head><title>405 Not Allowed</title></head>\r\n<body>\r\n<center><h1>405 Not Allowed</h1></center>\r\n<hr><center>nginx/1.18.0</center>\r\n</body>\r\n</html>\r\n" error="invalid character '<' looking for beginning of value"
Any idea's ?
Hi, Still getting this error with the latest version (2.4.0 )
kubectl logs -f subscriber-6ff65bc955-w8g69 -n litmus
time="2022-01-09T10:39:25Z" level=info msg="Go Version: go1.16.12"
time="2022-01-09T10:39:25Z" level=info msg="Go OS/Arch: linux/amd64"
time="2022-01-09T10:39:25Z" level=info msg="all deployments up"
time="2022-01-09T10:39:25Z" level=info msg="all components live...starting up subscriber"
time="2022-01-09T10:39:26Z" level=fatal msg="failed to parse cluster confirm data" data= error="unexpected end of JSON input"