Add dev/preview:create-preview

[mads-hartmann]

Description

TODO. Preview environments created in Werft works as expected, but from a workspace I get the following error:

leeway run dev/preview:create-preview
... a lot of output ...
/workspace/gitpod/dev/preview/infrastructure/harvester /workspace/gitpod/dev/preview
harvester_ssh_key.harvester_ssh_key: Creating...
╷
│ Error: Post "https://mads-add-l356b6c92d4.kube.gitpod-dev.com:6443/apis/harvesterhci.io/v1beta1/namespaces/preview-mads-add-l356b6c92d4/keypairs": EOF
│ 
│   with harvester_ssh_key.harvester_ssh_key,
│   on vm.tf line 59, in resource "harvester_ssh_key" "harvester_ssh_key":
│   59: resource "harvester_ssh_key" "harvester_ssh_key" {

Related Issue(s)

Part of https://github.com/gitpod-io/ops/issues/5766
Part of https://github.com/gitpod-io/ops/issues/5892

How to test

leeway run dev/preview:create-preview
leeway run dev/preview:delete-preview

Release Notes

NONE

Documentation

N/A

Werft options:

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-integration-tests=all
  Valid options are all, workspace, webapp, ide

[werft-gitpod-dev-com]

started the job as gitpod-build-mads-add-launch-preview-vm.1 because the annotations in the pull request description changed
(with .werft/ from main)

[vulkoingim]

Error: Post "https://mads-add-l356b6c92d4.kube.gitpod-dev.com:6443/apis/harvesterhci.io/v1beta1/namespaces/preview-mads-add-l356b6c92d4/keypairs": EOF

This looks like the address of the k3s cluster, not of the harvester cluster. I guess what's happening is that the default context in /home/gitpod/.kube/config is set to k3s at some point (when contexts are merged) and since the harvester provider just expects a kubeconfig path - not a context as well, it just uses the default one.

One thing you can do is kubectl config set-context harvester before running, but that doesn't guarantee that the default context won't get changed by some other process at some point. I would recommend having a separate config file just with the harvester context and using that one.

EDIT: Opened harvester/terraform-provider-harvester#55 on the harvester provider and if it gets accepted we'll be able to explicitly pass a context.

[meysholdt]

🚀