[installer]: validate the node labels by kind in config

[mrsimonemms]

Description

The Installer's validate cluster command checked the node labels as if the kind in the config file was always Full.

This removes this assumption and creates separate target affinities based upon the kind.

This PR is bigger than I'd hoped, but that's because I needed to move the checkAffinityLabels into the config/v1 package due to circular dependencies.

Related Issue(s)

Fixes #14598

How to test

• go run . config init
• Set the kind in gitpod.config.yaml to either Full, Meta or Workspace
• Run go run . validate cluster
• The affinity labels check should be as below...

Full

{
  "name": "affinity labels",
  "description": "all required affinity node labels [gitpod.io/workload_meta gitpod.io/workload_ide gitpod.io/workload_workspace_services gitpod.io/workload_workspace_regular gitpod.io/workload_workspace_headless] are present in the cluster",
  "status": "OK"
}

Meta

{
  "name": "affinity labels",
  "description": "all required affinity node labels [gitpod.io/workload_meta gitpod.io/workload_ide] are present in the cluster",
  "status": "OK"
}

Workspace

{
  "name": "affinity labels",
  "description": "all required affinity node labels [gitpod.io/workload_workspace_services gitpod.io/workload_workspace_regular gitpod.io/workload_workspace_headless] are present in the cluster",
  "status": "OK"
}

Release Notes

[installer]: validate the node labels by kind in config

Documentation

Werft options:

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

[Pothulapati]

Works as expected!