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

[self-hosted] Make our Self-Hosted terraform scripts infrastructure only #3912

Closed
geropl opened this issue Apr 13, 2021 · 3 comments
Closed
Assignees
Labels
priority: 💪 stretch goal This issue is a stretch goal within an iteration. self-hosted: eks Self hosted support for AWS EKS self-hosted type: bug Something isn't working

Comments

@geropl
Copy link
Member

geropl commented Apr 13, 2021

Currently our terraform scripts are geared towards a "one-step" install experience as they were meant to be included in the installer images. After we remove those images, we should try to make them work again by:

  • make the terraform scripts infrastructure only, without the actual Gitpod installation
  • thus make them work again (fix Wrong value of DB_ENCRYPTION_KEYS #3766 along the way)
  • update the docs to reflect the two-step nature:
    1. run provider-specific terraform script (output: values.terraform.yaml)
    2. run (generic) helm install

/cc @wulfthimm

@geropl geropl added type: bug Something isn't working self-hosted self-hosted: eks Self hosted support for AWS EKS priority: 💪 stretch goal This issue is a stretch goal within an iteration. labels Apr 13, 2021
@geropl geropl added this to the April 2021 milestone Apr 13, 2021
@geropl geropl self-assigned this Apr 13, 2021
@fullmetalrooster
Copy link
Contributor

That would be no problem.

@csweichel csweichel removed this from the April 2021 milestone May 6, 2021
@asthomasdk
Copy link

Would be nice to see this in action ;-)

I've been trying for most of a week now to get a working setup with my own terraform for a Hetzner K3s cluster, managed by Rancher 2.5 - and many iterations of trying to get gitpod to work on top of that. A clear set of (working) steps on how to go from zero to Gitpod hero on a simple infrastructure would be great to have.

@geropl
Copy link
Member Author

geropl commented Jul 8, 2021

This is issue is superseded by now.

@geropl geropl closed this as completed Jul 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: 💪 stretch goal This issue is a stretch goal within an iteration. self-hosted: eks Self hosted support for AWS EKS self-hosted type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants