Skip to content
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

Create HTTP Proxy preview in Werft #13028

Closed
8 tasks
Tracked by #13026
mrsimonemms opened this issue Sep 16, 2022 · 1 comment
Closed
8 tasks
Tracked by #13026

Create HTTP Proxy preview in Werft #13028

mrsimonemms opened this issue Sep 16, 2022 · 1 comment
Labels
meta: stale This issue/PR is stale and will be closed soon

Comments

@mrsimonemms
Copy link
Contributor

mrsimonemms commented Sep 16, 2022

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

  • All requirements as per the airgapped automation
  • 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).
@stale
Copy link

stale bot commented Dec 16, 2022

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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Dec 16, 2022
@stale stale bot closed this as completed Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: stale This issue/PR is stale and will be closed soon
Projects
No open projects
Development

No branches or pull requests

1 participant