http/https proxy ENV in helm chart

[bcg62]

currently it looks like there's no way to apply proxy settings, or additional env vars in general to the deployment.

simple things like:
command: ["sh", "-c", "apk --no-cache add curl.... will fail in a cluster that does not have direct internet access

[ghost]

@bcg62 yes, currently OpenShift and Kubernetes infras lack this feature.

@skabashnyuk I label this as a bug, since OpenShift/K8S cluster behind a proxy will be a common use case. While Docker infra implementation handles it OK, we should think of doing the same in OpenShift/K8S:

1. Add http_proxy, https_proxy and no_proxy to Che server, Keycloak and workspace containers.
2. Add JVM args for Che server and workspace agent.

[artaleks9]

Still actual for ver.6.6.0

[slemeur]

@eivantsov : I think you have a way to handle this. Has this been added to the documentation?

[ghost]

@slemeur no, not in docs yet. It felt somewhat wrong to document it, so I hoped some automation on server side was possible.

[ghost]

So, this is both a docs and eng task.

As the moment, the following envs work for Docker infra only:

CHE_WORKSPACE_HTTP__PROXY
CHE_WORKSPACE_HTTPS__PROXY
CHE_WORKSPACE_NO__PROXY

We need env provisioners for them. Once done, I can summarize in docs all the proxy envs that a user might need.

[ghost]

Will be fixed by #10387