Wait for the workspace secret before creating the workspace pod

[aledbf]

Description

We cannot expect any latency or that the load on the API server can provide time guarantees for object persistence.

default     0s          Normal    Scheduled                pod/ws-5d18c42e-c8eb-4db5-af28-4e9161927998           Successfully assigned default/ws-5d18c42e-c8eb-4db5-af28-4e9161927998 to i-09682c625b5eeb3fb.eu-central-1.compute.internal
default     0s          Normal    Pulling                  pod/ws-5d18c42e-c8eb-4db5-af28-4e9161927998           Pulling image "reg.doptig10.gitpod.cloud:20000/remote/5d18c42e-c8eb-4db5-af28-4e9161927998"
default     0s          Normal    Pulled                   pod/ws-5d18c42e-c8eb-4db5-af28-4e9161927998           Successfully pulled image "reg.doptig10.gitpod.cloud:20000/remote/5d18c42e-c8eb-4db5-af28-4e9161927998" in 97.809814ms
default     0s          Warning   Failed                   pod/ws-5d18c42e-c8eb-4db5-af28-4e9161927998           Error: secret "ws-5d18c42e-c8eb-4db5-af28-4e9161927998" not found

Related Issue(s)

Fixes https://github.com/gitpod-io/scout-foundation/issues/255

How to test

• Pass Integration tests
• Workspaces should open normally

Release Notes

NONE

Werft options:

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

[kylos101]

/werft run with-integration-tests=workspace with-large-vm=true

👍 started the job as gitpod-build-aledbf-wait-for-secret.1
(with .werft/ from main)

[aledbf]

/werft run with-integration-tests=workspace with-large-vm=true

👍 started the job as gitpod-build-aledbf-wait-for-secret.3
(with .werft/ from main)