Automation environments in Werft

[mrsimonemms]

As of today, Gitpodders have the ability to create a preview environment in Werft, either through /werft run preview or by selecting the checkbox in a PR. This is very helpful from a SaaS point of view, but there are options for self-hosted users that are not captured by this automation.

The intention at this stage is not to capture every single permutation of self-hosted installation type but to capture likely installation types that will be required for cross-team work.

Unless stated otherwise, the installations should be built in GCP. Self-Hosted definitions of terminology can be found here.

• Create AirGapped preview in Werft #13027
• Create HTTP Proxy preview in Werft #13028
• Add the new environments to the nightly tests #13030

Questions

• how will Werft/Harvester behave if a user creates multiple preview environments? /cc @gitpod-io/platform
• should these instances deploy Gitpod, or is it just the infrastructure that is then installed via KOTS? /cc @gitpod-io/engineering-self-hosted

---

The expectation is that these new environments will add a new line in the block at the bottom of a PR

[mrsimonemms]

See also RFC from Aleks

[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.