You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Build an automation in Werft that allows for creation of an airgapped Gitpod infrastructure with an HTTP Proxy that allows traffic to connect to the public internet. It must use the airgapped configuration as a base to prove that the connections are going via the proxy server and not leaking directly to the public internet. Unlike with airgapped, this cluster should still be able to connect to the public internet - it will get all container images from there and will be able to connect to a public GitHub/GitLab instance.
There should be both a Werft command (eg, /werft run proxy-preview) and a checkbox added to all PRs. This will also add an additional preview box under the PR.
Configuration of the Kubernetes cluster to a proxy server
GKE is not actually the requirement here. If easier to achieve via k3s, that would be acceptable
A proxy server
Squid seems to be a fairly simple server to configure
Access should be password protected, so the URL will be http://user:password@ip:3128
There is no requirement for HTTPS_PROXY - if no HTTPS_PROXY configured, use of the HTTP_PROXY is acceptable
The HTTP Proxy is currently provided to KOTS via --http-proxy, --https-proxy and --no-proxy flags. This data will need to be transferred securely (remember there will be a username/password in these values).
The text was updated successfully, but these errors were encountered:
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.
Build an automation in Werft that allows for creation of an airgapped Gitpod infrastructure with an HTTP Proxy that allows traffic to connect to the public internet. It must use the airgapped configuration as a base to prove that the connections are going via the proxy server and not leaking directly to the public internet. Unlike with airgapped, this cluster should still be able to connect to the public internet - it will get all container images from there and will be able to connect to a public GitHub/GitLab instance.
There should be both a Werft command (eg,
/werft run proxy-preview
) and a checkbox added to all PRs. This will also add an additional preview box under the PR.Requirements
http://user:password@ip:3128
HTTPS_PROXY
- if noHTTPS_PROXY
configured, use of theHTTP_PROXY
is acceptable--http-proxy
,--https-proxy
and--no-proxy
flags. This data will need to be transferred securely (remember there will be a username/password in these values).The text was updated successfully, but these errors were encountered: