-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[installer]: add HTTP_PROXY envvars to the Installer #12726
Conversation
4c3637c
to
208853e
Compare
/werft run 👍 started the job as gitpod-build-sje-installer-proxy-config.5 |
6cd0c30
to
ef3867d
Compare
ef3867d
to
a9c91bb
Compare
a9c91bb
to
ee71ee5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
started the job as gitpod-build-sje-installer-proxy-config.26 because the annotations in the pull request description changed |
Waiting for the build ☝️ to see if the default case is running. |
…vvar The @grpc/grpc-node package does not support wildcards in the no_proxy envvar. Add the FQDN's for the components that the server calls to the no_grpc_proxy envvar so that these calls are not proxied
ee71ee5
to
67a8365
Compare
@@ -122,6 +125,20 @@ func deployment(ctx *common.RenderContext) ([]runtime.Object, error) { | |||
}, | |||
) | |||
|
|||
if ctx.Config.HTTPProxy != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@geropl have updated as-per your comment 👍🏻
/werft run 👍 started the job as gitpod-build-sje-installer-proxy-config.28 |
started the job as gitpod-build-sje-installer-proxy-config.29 because the annotations in the pull request description changed |
67a8365
to
f791db5
Compare
started the job as gitpod-build-sje-installer-proxy-config.31 because the annotations in the pull request description changed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(WebApp related) Code LGTM, tested the preview and workspaces still start 🙃 ✔️
Thanks @geropl |
Description
Adds preliminary support for
HTTP_PROXY
(andHTTPS_PROXY
andNO_PROXY
) in the Installer. This adds an optional secret which receives the proxy settings from the KOTS CLI settings - theNO_PROXY
envvar also hard-codes some additional parameters required for the application to work.Important - this is not a full feature. It is merely the initial work to enable other teams to help out in their areas of expertise. This adds the appropriate envvars to the resources and wires them all up in a fashion that allows the Gitpod stack to run without error. However, it DOES NOT allow an image to be built or workspace to be run. There are additional tickets in #10769 that detail these tasks
An interesting thing of note is that the
@grpc/grpc-node
library does not respect wildcardNO_PROXY
URLs. To address that, theserver
adds an additionno_grpc_proxy
(which is the primary envvar for this library) and changes all resources it calls to the FQDN. See the issue for more details.Related Issue(s)
Fixes #12835
Fixes #12820
Fixes #12821
How to test
kubectl kots install gitpod --http-proxy <http-proxy> --https-proxy <https-proxy> --no-proxy <no-proxy>
to install GitpodConfiguring your cluster
A repo exists that will create a k3s cluster for you in Azure. Run
make azure-k3s
with the following settings in your.auto.tfvars
fileRelease Notes
Documentation
Werft options: