Add possibility to configure corporate proxy to reach ChaosHub

[cazeaux]

Hello,

When we use Litmus Chaos in a private Kubernetes cluster where a HTTP PROXY is required to reach the internet, it is not possible to reach the Chaos Hub (from Litmus portal) when the URL is on internet (typically github).
Using an internal private Chaos Hub is a possible workaround, but I would like to evaluate the possible support for corporate proxy.

Suggestions to support HTTPS PROXY:

• Either as part of the Chaos Hub configuration in Litmus portal
• Or more simply with a dedicate ENV variable to be set on graphql-server container

[avaakash]

Hi, @cazeaux, thanks for the suggestion, we will consider this for a future release. Meanwhile, if possible, would you like to try fixing this?

[gioppoluca]

is this solved? I cannot get to ChaosHub from a portal behind corporate proxy

[celinegrn]

Hi @avaakash, is there a workaround? I have the same problem with Litmus 3.11.0.
I do not have internet access and configuring https_proxy does not work as expected.

apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: litmus
  namespace: litmus
spec:
  interval: 1m
  chart:
    spec:
      chart: litmus
      sourceRef:
        kind: HelmRepository
        name: litmus
        namespace: litmus
  values:
     portal:
       server:
         graphqlServer:
           genericEnv:
             https_proxy: x