[preview] fix wait, diff-apply, regression-check slack

[vulkoingim]

Description

Fixes:

• [preview] Apply gitpod/monitoring-satellite resources if there's diff #16517 (comment)
  • added serve-side apply
• https://gitpod.slack.com/archives/C032A46PWR0/p1678732041625199
  • rollout status will wait for the resources, not individual pods
• https://github.com/gitpod-io/gitpod/actions/runs/4415644835
  • fix getting the secret from secret manager
• https://gitpod.slack.com/archives/C032A46PWR0/p1678800928661759
  • don't cancel the configuration job
• https://gitpod.slack.com/archives/C032A46PWR0/p1678867131515719
  • don't cancel build-gitpod as it confuses tide

Related Issue(s)

Fixes #

How to test

Release Notes

NONE

Documentation

Build Options:

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish Options

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer Options

• with-ee-license
• with-dedicated-emulation
• with-ws-manager-mk2
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment Options:

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

[werft-gitpod-dev-com]

started the job as gitpod-build-aa-wait-for-types-not-pods.1 because the annotations in the pull request description changed
(with .werft/ from main)

[werft-gitpod-dev-com]

started the job as gitpod-build-aa-wait-for-types-not-pods.2 because the annotations in the pull request description changed
(with .werft/ from main)

[kylos101]

@vulkoingim @mads-hartmann we are blocked from deploying, the Workspace Integration tests are failing, and we generally require tests to be green before deploying.

1. When triggered from werft, the preview create cannot find the werft namespace after doing many diffs.
   • I think that is related to this PR.
   • Can you help?
   • Being able to run again in werft until our new Workspace Integration Test GHA is stable would prove helpful for the team.
2. I tried running the tests manually as a workaround from /test via ./run.sh -s workspace, but, the preview environment appears to be in an odd state, which is resulting in test failures for minio and our content-service.
   • I plan to recreate the preview environment, and try again Friday to debug.
   • The errors for reference indicate a mismatch between the configured minio secret, and what content-service is using:

[test-workspace-parallel] === RUN   TestUploadDownloadBlob/UploadDownloadBlob/it_should_upload_and_download_blob
[test-workspace-parallel]     content-service_test.go:192: rpc error: code = NotFound desc = The Access Key Id you provided does not exist in our records.
[test-workspace-parallel] --- FAIL: TestUploadDownloadBlob (5.07s)
[test-workspace-parallel]     --- FAIL: TestUploadDownloadBlob/UploadDownloadBlob (5.07s)
[test-workspace-parallel]         --- FAIL: TestUploadDownloadBlob/UploadDownloadBlob/it_should_upload_and_download_blob (5.07s)

[test-workspace-parallel]     content_test.go:397: rpc error: code = Unknown desc = The Access Key Id you provided does not exist in our records.
[test-workspace-parallel] --- FAIL: TestMissingBackup (24.81s)
[test-workspace-parallel]     --- FAIL: TestMissingBackup/CreateWorkspace (24.81s)
[test-workspace-parallel]         --- FAIL: TestMissingBackup/CreateWorkspace/it_ensures_workspace_fail_if_they_should_have_a_backup_but_don't_have_one (24.81s)

@corneliusludmann for 👀