allow for injection of envvars into imagebuild/workspace templates from the Installer

[mrsimonemms]

As part of the Installer work to introduce support for HTTP_PROXY, we have created a ProxyEnv function that injects the six envvars from a customisable secret - see code.

Both the imagebuild and workspace templates require these six envvars in the workspace.

It would be a useful feature if we could add envvars into the workspace template configmap. This would allow for the envvars to be injected into the workspace so that the actual configuration can be driven by the Installer without having to repeat the functionality in multiple parts of the codebase.

[kylos101]

@mrsimonemms it seems like we're much closer than I realized to having a feedback loop that support the proxy use case!

1. ✔️ a self-hosted environment built with kots, this is 🚀 awesome!
2. ✅ kots proxy support in the Gitpod product. 🙏 thank you so much!
3. ❓ the werft job introduced in [installer-preview] add werft flags for triggering self-hosted preview #12229 be updated to support proxy use cases (where all egress must go through the proxy server)

After which, I think we'd be in a position to iterate quite nicely. @mrsimonemms and @corneliusludmann , can you share an ETA for when the werft job may support the proxy use case, and an alternative set of instructions we can use for the interim? Having either will make it possible for us to Schedule this work for Team Workspace.

edit: I was thinking about point 3, above. It seems like the bit that is missing, is how to restrict an environment, so that it's only using the proxy server from point 2. Being able to do that manually (with instructions), or automatically (via a werft job) would unblock the Workspace Team, so that we can Schedule this work.

[mrzarquon]

We can't assume the proxies used for services are the same proxies users want in their workspaces. Either for security or tracking purposes users may have to configure different proxies for a 'live' workspace vs proxies used for gitpod's purposes.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.