[ws-manager-mk2] Extract headless task failure (WKS-18)

[WVerlaek]

Description

• If a headless task container exits with a non-empty Message, consider it a failure (as we do with mk1).
• Always log workspace status in reconciliations. We can disable at a later point, but without it it becomes almost impossible to debug workspace/pod state changes.
  • In addition, also log the pod status

Related Issue(s)

How to test

In a preview env, create an image build, restart ws-daemon during the build (which currently causes the build to fail), and observe the workspace exits with a Failed condition and doesn't transition through Initializing after Running.

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-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
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

[Gaynelpaul1]

L

[Gaynelpaul1]

Good