Geo: Update how the Geo playbooks determines if it's configuring Cloud Native/Cloud Native Hybrid/Omnibus

Nick Westburyrequested to merge
geo_update_playbook_roles into main

What does this MR do?

This change updates the conditions that determine when GitLab Geo should be configured for Cloud Native or Cloud Native Hybrid / Omnibus. When deploying to just a Cloud Native deployment the playbooks only need to be run on localhost due to all configuration being handled via Helm.

Currently, the conditions are failing when deploying a Cloud Native Hybrid deployment that uses Gitaly in K8s. The conditions have been updated to check for the VM types that Geo actively configures.

Related issues

Author's checklist

When ready for review, the Author applies the workflowready for review label and mention @gitlab-org/software-delivery/get-maintainers:

  • Merge request:
    • Corresponding Issue raised and reviewed by the GET maintainers team.
    • Merge Request Title and Description are up-to-date, accurate, and descriptive
    • MR targeting the appropriate branch
    • MR has a green pipeline
    • MR has no new security alerts in the widget from the Secret Detection and IaC Scan (SAST) jobs.
  • Code:
    • Check the area changed works as expected across all expected permutations.
    • Check that the changes work across upgrades.
    • Documentation created/updated in the same MR if applicable

Merge request reports