[tests] tailscale integration test
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe
We lack integration tests that tell us about the health of our support for the tailscale feature.
Describe the behaviour you'd like
Our integration tests should assert that the tailscale integration, including support for DNS, is working as expected.
Describe alternatives you've considered
Continue doing manual testing.
Additional context
https://github.com/gitpod-io/workspace-images/pull/956
https://github.com/gitpod-io/website/pull/2908
https://github.com/gitpod-io/gitpod/issues/13785
Adding secrets to support this test.
- Add the secret to GCP (manually) in
gitpod-core-devproject - Copy the secret from GCP to core-dev with TF (docs)
- Copy the secret from core-dev to the preview environment as part of the deploy (example)
The secret you'll be storing is a tailscale key (authkey). It should be reusable (so it can support many preview VMs) and ephemeral (so when machines go offline from the tailscale network, that they are removed).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked workspace-images, website, and gitpod issues, then inspect dev/preview/workflow/preview/deploy-gitpod.sh and the referenced secret-deployment steps. Identify the existing integration-test entry point and determine how preview environments receive the Tailscale key. Done means integration tests cover Tailscale support, including DNS, with the required reusable and ephemeral secret configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, terraform
- Domain
- cloud, infrastructure, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100