Alternative to Port Forwarding for Accessing Litmus Portal UI

[sejalAmagi]

Hi everyone,

I have deployed LitmusChaos in my Kubernetes cluster and currently I am accessing the Litmus Portal UI using port forwarding:

kubectl -n litmus port-forward --address 0.0.0.0 svc/litmusportal-frontend-service 9091:9091

This allows me to open the UI locally using the forwarded port.

I wanted to know if there is an alternative way to expose the Litmus Portal so that other users can directly access the UI without needing to run port-forward on the cluster node.

Any guidance or best practices would be really helpful.

Thanks!

[M3shour]

Depending on your environment, you can expose it via a NodePort or an Ingress

[sejalAmagi]

Depending on your environment, you can expose it via a NodePort or an Ingress

Thanks for the suggestion!

I wanted to clarify something — is it possible to interact with Litmus Portal completely without using port-forward, for example by using the GraphQL API directly?

Right now I have a script that retrieves the Litmus namespace, and I was wondering if it’s also possible to perform other operations purely through the API, such as:

Changing the admin/user password

Retrieving or listing the infrastructure connected to the portal

My idea is to automate this using scripts instead of accessing the UI or running kubectl port-forward.

Is this a supported approach, or is exposing the portal through NodePort/Ingress still required for these API operations?

Thanks!

[nXtCyberNet]

Another possible approach could be using a Tailscale sidecar container alongside the Litmus Portal container to privately expose the portal API over a Tailnet, instead of relying on kubectl port-forward or exposing it through NodePort/Ingress.

The only trade-off would be a small increase in network latency, but that probably isn’t a big issue if your usecase allow it .