search

litmuschaos / litmus

Litmus helps SREs and developers practice chaos engineering in a Cloud-native way. Chaos experiments are published at the ChaosHub (https://hub.litmuschaos.io). Community notes is at https://hackmd.io/a4Zu_sH4TZGeih-xCimi3Q
https://litmuschaos.io
Apache License 2.0
4.42k stars 692 forks source link

Fix agent connectivity for control plane exposed via non nginx-controller based ingress #3597

Open ksatchit opened 2 years ago

ksatchit commented 2 years ago

Today, litmus supports the successful resolution of server address (SERVER_ADDR on the agent-config configmap) in cases where the nginx ingress controller is used (ref: https://docs.litmuschaos.io/docs/user-guides/setup-with-ingress/#install-chaoscenter-with-ingress). However, this same capability is not extended to other ingress types (AWS ALB, Trafeik, istio gateway etc.,).

This issue tracks a need for a generic solution that would enable successful setup/connectivity of agent regardless of the ingress type used.

ksatchit commented 2 years ago

A proposed solution is to use a tunable (env) on the chaos server deployment (say, SERVER_URL) that can be injected into the config as part of agent setup. Refer to conversations within the community regarding this, here: https://kubernetes.slack.com/archives/CNXNB0ZTN/p1651590192986229