Holodeck 9.1 Click-to-Deploy GitOps — Part 2: Full Site A VCF 9.1.0.0 Deployment from the UI

Written for Holodeck Toolkit 9.1 GA deploying VCF 9.1.0.0 Site A. The same UI/pipeline flow applies to VVF 9.1.0.0 and down-rev targets to VCF 5.2 with different content selections. NSX and component build numbers ship inside the VCF 9.1.0.0 content and are not independently selected in this flow — record the deployed component versions during validation (verify_live). This is the 9.1 parallel twin of holodeck-02's deployment tasks; the 9.0.x cmdlet-driven deployment remains documented in holodeck-02 and is not superseded.

Objectives

• Read and interpret the auto-provisioned deployment pipeline definition before trusting it with a multi-hour build
• Trigger a full Site A VCF 9.1.0.0 deployment from the Click-to-Deploy UI without executing any manual PowerShell
• Monitor a running deployment across all three observation planes: GitLab pipeline jobs, vSphere inventory on the physical host, and the VCF installer UI
• Validate the deployed management domain end to end (SDDC Manager, vCenter, NSX) to the same health bar as the 9.0 track
• Treat the Git history and pipeline record as the deployment's evidence chain, and assess the GitOps loop for drift and repeatability
• Extend the verify-live findings log with pipeline-stage mapping and deployed component versions

Prerequisites

Lab Environment

graph TB
  WS[Operator Workstation] -->|HTTPS| GL[GitLab on HoloRouter 9.1<br/>Click-to-Deploy UI]
  GL -->|pipeline run| PIPE[Deployment Pipeline]
  PIPE --> ESX1[Nested ESX-01 10.1.1.101]
  PIPE --> ESX2[Nested ESX-02 10.1.1.102]
  PIPE --> ESX3[Nested ESX-03 10.1.1.103]
  PIPE --> ESX4[Nested ESX-04 10.1.1.104]
  PIPE --> INST[VCF Installer 10.1.1.200 - verify live]
  INST --> SDDC[SDDC Manager 10.1.1.4]
  INST --> VC[vCenter 10.1.1.6]
  INST --> NSX[NSX Manager 10.1.1.10]
  HR[HoloRouter 9.1<br/>Technitium DNS / gateway] --- ESX1
  HR --- SDDC

Tasks

Final Validation

Cleanup / Restore

Design Reflection (VCDX)

Self-Assessment Discussion Prompts

1. Compare your measured 9.1 pipeline deployment against the holodeck-02 cmdlet deployment across: operator time invested, wall-clock time, evidence produced, and skill floor required. Where does each path win?
2. Repeatability: the cmdlet path re-run depends on the operator re-executing steps identically; the pipeline re-run depends on the same commit producing the same result. Which failure modes does each dependence create, and which did you actually observe?
3. Auditability: your evidence chain links commit to running estate. A panelist asks 'could an operator have made the estate diverge from that commit without leaving a trace?' Answer honestly from your drift-probe result, and design the control that closes whatever gap you found.
4. Drift: is the 9.1 toolkit a reconciling GitOps system or a versioned trigger system, per your Task 5 observation? What operational practice must you add in the second case to keep Git truthful?
5. The pipeline failed at the nested-ESX stage for a colleague (datastore misnamed in the committed config). Walk through the recovery: what gets fixed where, what gets cleaned up, and what does the Git history look like afterwards if done properly?
6. Your reproduction recipe still contains tribal-knowledge items from the findings log. For each, decide: automate it, document it into the repo, or accept it — and justify the split as you would in a design defense.
7. In production VCF, would you accept a deployment system whose control plane (GitLab) lives inside the failure domain it deploys (on the router of the estate)? Map this to production analogs and state your placement decision.

Extensions

References

• HoloDeck 9.1 Release Announcement (verbatim capture) Holodeck-9.1/01-release-announcement.mdlocal fileTier 1 — Official
  Primary source: 'trigger full Holodeck deployments directly from the UI — no manual PowerShell required'; VCF 9.1.0.0 support; hardened VCF installer validation.
• HoloDeck Toolkit 9.1 — Structured Reference & Changelog Holodeck-9.1/02-structured-changelog.mdlocal fileTier 1 — Official
  9.0-to-9.1 orientation table (deployment driver: PowerShell -> GitOps/UI) and open-questions list tracked by this lab's findings log.
• VCF 9.1 Release Intake — rn-9-1-016 (Click-to-Deploy GitOps) academy-v2/content/releases/vcf-9.1.jsonlocal fileTier 1 — Official
  Confirms both paths must be presented in lab guidance: GitOps/UI (this lab) and cmdlets (holodeck-02 remains the 9.0.x record).
• VMware Cloud Foundation Documentation (Broadcom)Tier 1 — Official
  Authoritative VCF documentation portal — consult the 9.1 deployment and bring-up guides for component-level detail as they publish.
• VCF Holodeck Toolkit — Broadcom Community ForumTier 1 — Official
  All captured KB threads are 9.0-era. Deployment-phase failure classes (datastore, legacy CPU, installer readiness) are referenced here as carried-over hypotheses, not confirmed 9.1 behavior.
• GitLab CI/CD Pipelines DocumentationTier 2 — VMware Press
  For reading pipeline graphs, job logs, and run metadata used throughout Tasks 1-3 and the evidence chain in Task 5.
• OpenGitOps PrinciplesTier 2 — VMware Press
  Framework for the Task 5 drift probe: distinguishing a reconciling GitOps system from a versioned trigger system.