[installer-tests] Fix GCP database config

[nandajavarma]

Description

Currently the database config for GCP is buggy. The config is missing some important details and hence on nightly tests with external database as dependency, the tests fail. This PR fixes these issues. This fixes the KOTS config with the right field names and takes the output from the GKE and k3s modules to apply them respectively.

Related Issue(s)

Fixes #

How to test

werft run github -j .werft/gke-installer-tests.yaml -a skipTests=true -a deps=external
werft run github -j .werft/k3s-installer-tests.yaml -a skipTests=true -a deps=external

Release Notes

NONE

Documentation

Werft options:

• /werft with-preview

[adrienthebo]

Looks like europe-west1 is overloaded:

job ref

Error: ╷
│ Error: Error waiting for instance to create: The zone 'projects/sh-automated-tests/zones/europe-west1-b' does not have enough resources available to fulfill the request.  '(resource type:compute)'.
│
│
│   with module.k3s.google_compute_instance.k3s_master_instance,
│   on ../infra/modules/k3s/main.tf line 69, in resource "google_compute_instance" "k3s_master_instance":
│   69: resource "google_compute_instance" "k3s_master_instance" {
│
╵
make: *** [Makefile:127: k3s-standard-cluster] Error 1

Trying to send slack alert
tracing warning: No slice span by name create-gcp-infra

[adrienthebo]

GKE

Looks good, setup and teardown worked job link

Rerunning k3s now.

[adrienthebo]

k3s tests timed out and failed, re-running

[nandajavarma]

@adrienthebo Doing a quick rebase with main. Just so it would pick up the tf changes in case that is what is causing this

[nandajavarma]

Yet another failed k3s setup.. Looks like someone else using k3sup ran into the same thing. See this issue comment opened 3 hours ago. Not sure if using --local is a solution for us. Will try this maybe

[adrienthebo]

Wow, that's a weird one, I'm surprised that this suddenly popped up out of nowhere. No rush on this though, we can tackle it on Monday :)

[alexellis]

Hi folks, if you're using k3sup for GitPodGitpod, your support would be appreciated.

The error is due to a validation change, which has since been fixed.

I'd suggest you pin the version of k3sup that you use, rather than tracking the latest binary, then upgrade it when you have time to verify newer versions.

cc @mrsimonemms

Alex