Developer Ready Infrastructure for VMware Cloud Foundation
Design, implementation, and operational guidance for a VI workload domain that runs vSphere with Tanzu workloads. Activates a Supervisor on the shared edge and workload vSphere cluster, uses the Tanzu Kubernetes Grid Service to deploy Tanzu Kubernetes clusters, and provides guidance for capacity, scalability, backup, and disaster recovery support. Enables Kubernetes natively on vSphere.
Key Components: NSX, SDDC Manager, vCenter, ESXi, Tanzu
External dependencies: None (vSphere with Tanzu and Tanzu Kubernetes Grid Service are part of VCF)
26 design decisions. The Quality column is the Academy's assessment for defence practice; the VVS documents do not classify decisions by design quality (D133).
| DD-ID | Decision | Quality (Academy view) |
|---|---|---|
| DRI-TZU-CFG-001 | Create a vSphere tag and tag category, and apply the vSphere tag to the vSAN datastore in the… | Manageability |
Decision: Create a vSphere tag and tag category, and apply the vSphere tag to the vSAN datastore in the shared edge and workload vSphere cluster in the VI workload domain. Rationale: Supervisor activation requires the use of vSphere Storage Based Policy Management (SPBM). To assign the vSAN datastore to the Supervisor, you need to create a vSphere tag and tag category to create an SPBM rule. Implication: This must be done manually or via PowerCLI. Component: TZU | ||
| DRI-TZU-CFG-002 | Create a vSphere Storage Policy Based Management (SPBM) policy that specifies the vSphere tag you… | Manageability |
Decision: Create a vSphere Storage Policy Based Management (SPBM) policy that specifies the vSphere tag you created for the Supervisor. Rationale: When you create the SPBM policy and define the vSphere tag for the Supervisor, you can then assign that SPBM policy during Supervisor activation. Implication: This must be done manually or via PowerCLI. Component: TZU | ||
| DRI-TZU-CFG-003 | Activate vSphere with Tanzu on the shared edge and workload vSphere cluster in the VI workload… | PerformanceManageability |
Decision: Activate vSphere with Tanzu on the shared edge and workload vSphere cluster in the VI workload domain. Rationale: The Supervisor is required to run Kubernetes workloads natively and to deploy Tanzu Kubernetes clusters natively using Tanzu Kubernetes Grid Service. Implication: Ensure the shared edge and workload vSphere cluster is sized to support the Supervisor control plane, any additional integrated management workloads, and any tenant workloads. Component: TZU | ||
| DRI-TZU-CFG-004 | Deploy the Supervisor with small size control plane nodes. | Performance |
Decision: Deploy the Supervisor with small size control plane nodes. Rationale: Deploying the control plane nodes as small size appliances gives you the ability to run up to 2000 pods within your Supervisor. If your pod count is higher than 2000 for the Supervisor, you must deploy control plane nodes that can handle that level of scale. Implication: You must account for the size of the control plane nodes. Component: TZU | ||
| DRI-TZU-CFG-005 | Use NSX as provider of the software-defined networking for the Supervisor. | Manageability |
Decision: Use NSX as provider of the software-defined networking for the Supervisor. Rationale: You can deploy a Supervisor either by using NSX or vSphere Networking. VMware Cloud Foundation uses NSX for softwaredefined networking across the SDDC. Deviating for vSphere with Tanzu would increase the operational overhead. Implication: None. Component: TZU | ||
| DRI-TZU-CFG-006 | Deploy the NSX Edge cluster with large size nodes. | Performance |
Decision: Deploy the NSX Edge cluster with large size nodes. Rationale: Large size NSX Edge nodes are the smallest size supported to activate a Supervisor. Implication: You must account for the size of the NSX Edge nodes. Component: TZU | ||
| DRI-TZU-CFG-007 | Deploy a single-zone Supervisor. | Availability |
Decision: Deploy a single-zone Supervisor. Rationale: A three-zone Supervisor requires three disparate vSphere clusters. Implication: No change to existing design or procedures with single-zone Supervisor. Component: TZU | ||
| DRI-TZU-CFG-008 | Deploy Contour as an Ingress Supervisor Service. | Manageability |
Decision: Deploy Contour as an Ingress Supervisor Service. Rationale: Harbor requires Contour on the target Supervisor to provide Ingress Service. The Ingress IP address provided by Contour must be resolved to the Harbor FQDN. Implication: None. Component: TZU | ||
| DRI-TZU-CFG-009 | Deploy the Harbor Registry as a Supervisor Service. | Manageability |
Decision: Deploy the Harbor Registry as a Supervisor Service. Rationale: Harbor as a Supervisor Service has replaced the integrated registry in previous vSphere versions. Implication: You must provide the following configuration: • Harbor FQDN • Record and Pointer Record (PTR) for the Harbor Registry IP (this IP is provided by the Contour Ingress Service) • Manage Supervisor Services privilege in vCenter Server. Component: TZU | ||
| DRI-TZU-CFG-010 | Deploy a Tanzu Kubernetes Cluster in the Supervisor. | Manageability |
Decision: Deploy a Tanzu Kubernetes Cluster in the Supervisor. Rationale: For applications that require upstream Kubernetes compliance, a Tanzu Kubernetes Cluster is required. Implication: None Component: TZU | ||
| DRI-TZU-CFG-011 | For VMware Cloud Foundation 4.5.2 or earlier, configure a subscribed content library for Tanzu… | Manageability |
Decision: For VMware Cloud Foundation 4.5.2 or earlier, configure a subscribed content library for Tanzu Kubernetes Cluster use in the shared edge and workload vSphere cluster. Rationale: In VMware Cloud Foundation 4.5.2 or earlier, to deploy a Tanzu Kubernetes Cluster on a Supervisor, you must configure a content library in the shared edge and workload vSphere cluster to pull required images from VMware. This is done automatically as part of the Supervisor instantiation process in VMware Cloud Foundation 5.0 or later. Implication: You must manually configure the content library in VMware Cloud Foundation 4.5.2 or earlier. Component: TZU | ||
| DRI-TZU-CFG-012 | Use Antrea as the container network interface (CNI) for your Tanzu Kubernetes Clusters. | Manageability |
Decision: Use Antrea as the container network interface (CNI) for your Tanzu Kubernetes Clusters. Rationale: Antrea is the default CNI for Tanzu Kubernetes Clusters. Implication: New Tanzu Kubernetes Clusters are deployed with Antrea as the CNI, unless you specify Calico. Component: TZU | ||
| DRI-TZU-CFG-013 | Deploy the Tanzu Kubernetes Cluster with a minimum of three control plane nodes. | Availability |
Decision: Deploy the Tanzu Kubernetes Cluster with a minimum of three control plane nodes. Rationale: Deploying three control plane nodes ensures the state of your Tanzu Kubernetes Cluster control plane stays healthy in the event of a node failure. Implication: None. Component: TZU | ||
| DRI-TZU-CFG-014 | Deploy the Tanzu Kubernetes Cluster with a minimum of three worker nodes. | Availability |
Decision: Deploy the Tanzu Kubernetes Cluster with a minimum of three worker nodes. Rationale: Deploying three worker nodes provides a higher potential level of availability of your workloads deployed to the Tanzu Kubernetes Cluster. Implication: You must configure your tenant workloads to use effectively the additional worker nodes in the Tanzu Kubernetes Cluster to provide high availability on an application-level. Component: TZU | ||
| DRI-TZU-CFG-015 | Deploy the Tanzu Kubernetes Cluster with small-size nodes for both control plane and workers. | Performance |
Decision: Deploy the Tanzu Kubernetes Cluster with small-size nodes for both control plane and workers. Rationale: Deploying the Tanzu Kubernetes Cluster control plane and worker nodes as small-size appliances meets the scale requirements for most deployments. If your scale requirements are higher, you must deploy appliances with the appropriate size or split the workload to multiple Tanzu Kubernetes Clusters. Implication: The size of the Tanzu Kubernetes Cluster nodes impacts the scale of a given cluster. If you must add a node to a cluster, consider the use of larger nodes. Component: TZU | ||
| DRI-TZU-NET-001 | Add a /24 overlay-backed NSX segment for use by the Supervisor control plane nodes. | Manageability |
Decision: Add a /24 overlay-backed NSX segment for use by the Supervisor control plane nodes. Rationale: Supports the Supervisor control plane nodes. Implication: You must create the overlaybacked NSX segment. Component: TZU | ||
| DRI-TZU-NET-002 | Use a dedicated /20 subnet for pod networking. | PerformanceManageability |
Decision: Use a dedicated /20 subnet for pod networking. Rationale: A single /20 subnet is sufficient to meet the design requirement of 2000 pods. Implication: Private IP space behind a NAT that you can use in multiple Supervisors. Component: TZU | ||
| DRI-TZU-NET-003 | Use a dedicated /22 subnet for services. | PerformanceManageability |
Decision: Use a dedicated /22 subnet for services. Rationale: A single /22 subnet is sufficient to meet the design requirement of 2000 pods. Implication: Private IP space behind a NAT that you can use in multiple Supervisors. Component: TZU | ||
| DRI-TZU-NET-004 | Use a dedicated /24 or larger subnet on your corporate network for ingress endpoints. | PerformanceManageability |
Decision: Use a dedicated /24 or larger subnet on your corporate network for ingress endpoints. Rationale: A /24 subnet is sufficient to meet the design requirement of 2000 pods in most cases. Implication: This subnet must be routable to the rest of the corporate network. A /24 subnet will suffice for most use cases, but you should evaluate your ingress needs prior to deployment. Component: TZU | ||
| DRI-TZU-NET-005 | Use a dedicated /24 or larger subnet on your corporate network for egress endpoints. | PerformanceManageability |
Decision: Use a dedicated /24 or larger subnet on your corporate network for egress endpoints. Rationale: A /24 subnet is sufficient to meet the design requirement of 2000 pods in most cases. Implication: This subnet must be routable to the rest of the corporate network. A /24 subnet will suffice for most use cases, but you should evaluate your egress needs prior to deployment. Component: TZU | ||
| DRI-TZU-SEC-001 | Create a security group in Active Directory for DevOps administrators. Add users who need edit… | Security |
Decision: Create a security group in Active Directory for DevOps administrators. Add users who need edit permissions within a namespace to the group and grant Can Edit permissions to the namespace for that group. If you require different permissions per namespace, create additional groups. Rationale: Necessary for auditable rolebased access control within the Supervisor and Tanzu Kubernetes clusters. Implication: You must define and manage security groups, group membership, and security controls in Active Directory. Component: TZU | ||
| DRI-TZU-SEC-002 | Create a security group in Active Directory for DevOps administrators. Add users who need read-only… | Security |
Decision: Create a security group in Active Directory for DevOps administrators. Add users who need read-only permissions in a namespace to the group, and grant Can View permissions to the namespace for that group. If you require different permissions per namespace, create additional groups. Rationale: Necessary for auditable rolebased access control within the Supervisor and Tanzu Kubernetes clusters. Implication: You must define and manage security groups, group membership, and security controls in Active Directory. Component: TZU | ||
| DRI-TZU-SEC-003 | Replace the default selfsigned certificate for the Supervisor management interface with a… | Security |
Decision: Replace the default selfsigned certificate for the Supervisor management interface with a PEMencoded, CA-signed certificate. Rationale: Ensures that the communication between administrators and the Supervisor management interface is encrypted by using a trusted certificate. Implication: Replacing and managing certificates is an operational overhead as it must be done outside of SDDC Manager certificate automation. Component: TZU | ||
| DRI-TZU-SEC-004 | Use a SHA-2 or higher algorithm when signing certificates. | Security |
Decision: Use a SHA-2 or higher algorithm when signing certificates. Rationale: The SHA-1 algorithm is considered less secure and has been deprecated. Implication: Not all certificate authorities support SHA-2. Component: TZU | ||
| DRI-TZU-LCM-001 | Life cycle management of a Supervisor is performed using the vSphere Client with its native… | Manageability |
Decision: Life cycle management of a Supervisor is performed using the vSphere Client with its native workflows. Rationale: Life cycle management of a Supervisor is not integrated into SDDC Manager. Implication: Deployment, patching, updates, and upgrades of a Supervisor and its components subject to update or upgrade are performed without SDDC Manager automation. Component: TZU | ||
| DRI-TZU-LCM-002 | Life cycle management of a Tanzu Kubernetes cluster is performed using kubectl. | Manageability |
Decision: Life cycle management of a Tanzu Kubernetes cluster is performed using kubectl. Rationale: Life cycle management of a Tanzu Kubernetes cluster is not integrated into SDDC Manager. Implication: Deployment, patching, updates, and upgrades of a Tanzu Kubernetes cluster and its components subject to update or upgrade are performed without SDDC Manager automation. Component: TZU | ||
Prerequisites
- VCF version listed in Support Matrix (5.1.0-5.2.1)
- Environment configured per Before You Apply This Guidance
- Developer Ready Infrastructure tab completed in VCF Planning and Preparation Workbook
- VCF instance healthy and fully operational
- If using stretched vSAN: all vSAN datastores healthy including witness hosts
- DNS forward/reverse records
- AD DCs available; service accounts and security groups created
- Microsoft CA available with PowerShell Module installed
- OpenSSL 3.0+ on PowerShell host
- PowerShell 7.2+ installed
- NSX Edge cluster deployed with LARGE-sized nodes (required for Supervisor)
- Workload domain NSX preparation complete
- PowerShell Automation
- Workflow
Implementation Procedure
PowerShell implementation (VVS 1.0 p.154)
- Install modules (VMware.PowerCLI 13.2.1+, vSphere.SsoAdmin 1.3.9+, ImportExcel 7.8.5+, PowerVCF 2.4.0+, PowerValidatedSolutions 2.11.0+)
- Create folder structure and place completed P&P Workbook
- Run Start-ValidatedSolutionMenu
- From the main menu, enter 05. (DRI) Developer Ready Infrastructure
- Enter 01. Generate JSON Specification File
- Enter 02. Verify Prerequisites
- Enter 05. End-to-End Deployment
UI implementation steps
- VCF 4.5.2 and earlier only: configure a subscribed content library in the shared edge and workload cluster of the VI workload domain (DRI-TZU-CFG-011). In VCF 5.0 and later the content library is created automatically during Supervisor activation — no manual step.
- Configure Storage Policies (vSphere Storage Policy for Tanzu) — vSAN or tagged
- Deploy large-sized NSX Edge cluster via SDDC Manager
- Activate Supervisor on shared edge/workload cluster using vSphere Client (Menu > Workload Management > Add Cluster)
- Configure Supervisor control plane size (Tiny/Small/Medium/Large per desired pod scale)
- Configure Supervisor networking: mgmt network, pod/service/ingress/egress CIDRs
- Create vSphere namespaces; assign storage policies, CPU/memory limits, permissions to AD groups
- Install Supervisor Services: Harbor (Registry), Contour (Ingress)
- Replace Supervisor Kubernetes API endpoint certificate with CA-signed cert
- Deploy Tanzu Kubernetes Clusters via kubectl + TKC YAML manifests (using TanzuKubernetesCluster CRD or ClusterClass)
- License Supervisor (Tanzu Supervisor license)
- Add additional VM Classes for TKC (e.g., GPU-enabled classes)
External services / integration points
- Active Directory (LDAP)
- DNS
- NTP
- Certificate Authority
Implementation options
| Method | Description |
|---|---|
| PowerShell automation | PowerValidatedSolutions menu 05. (DRI) Developer Ready Infrastructure |
| UI / component interfaces | vSphere Client Supervisor deployment workflow + kubectl for TKC |
Personas
| Persona | Responsibility | Component role or group |
|---|---|---|
| vSphere Administrator | Full administrative access to the vSphere with Tanzu infrastructure: configures and activates Supervisors and vSphere namespaces | vCenter Server: Administrator |
| DevOps Engineer | Deploys vSphere Pods, VMs and Tanzu Kubernetes clusters on existing vSphere namespaces within a Supervisor | vSphere namespace: Can edit (DRI-TZU-SEC-001 AD group) |
| Auditor | Read-only access for security and compliance review | vSphere namespace: Can view (DRI-TZU-SEC-002 AD group) |
Day-2 Operations Tasks
Certificate management — Supervisor Kubernetes API endpoint
Before expiry, on compromise or attribute changeIn the vSphere Client create the CSR for the Supervisor Kubernetes API endpoint, have the CA sign it with SHA-2 or higher (DRI-TZU-SEC-003/004), import the certificate in the vSphere Client; afterwards kubectl vsphere login works without --insecure-skip-tls-verify on TCP/443 and TCP/6443 (VVS 1.0 pp.154-155).
Password management
Per VCF password policyESXi, vCenter, NSX and SDDC Manager passwords rotate through SDDC Manager (Manage Passwords); Supervisor and Tanzu Kubernetes Grid Service authentication follows vSphere with Tanzu authentication (vCenter SSO / AD groups), so there are no separate appliance passwords to rotate.
Scale up — resize Supervisor control plane nodes
When pod or cluster counts approach the size limitResize the three control plane nodes to the next size (Tiny 2 vCPU/8 GB/1000 pods, Small 4/16/2000, Medium 8/24/4000, Large 16/32/8000 — Table 121) and account for the extra CPU and memory in the shared edge and workload cluster.
Scale out — additional Supervisors or clusters
When a single vSphere cluster is exhaustedAdd hosts to the shared edge and workload cluster, or activate a Supervisor on an additional cluster in the VI workload domain; each Supervisor needs its own NSX Edge cluster capacity (large nodes, DRI-TZU-CFG-006) and network ranges (DRI-TZU-NET-001..005).
Backup with Velero
Scheduled (Velero CLI schedules) and before changesInstall the Velero plug-in for vSphere and the Velero Data Manager, then create one-off and scheduled backups of Kubernetes objects and Tanzu Kubernetes clusters with the Velero CLI; after a Supervisor rebuild, restore individual Kubernetes components from the existing Velero backups (pp.164-165).
Life cycle management
Per releaseSupervisor life cycle through the vSphere Client native workflows (DRI-TZU-LCM-001, not SDDC Manager); Tanzu Kubernetes cluster upgrades with kubectl by changing the cluster spec version (DRI-TZU-LCM-002).
Monitoring
ContinuousVCF Operations native integration monitors the Supervisor and the Tanzu Kubernetes clusters; watch control plane node capacity against the Table 121 pod limits and NSX Edge utilisation.
Monitoring Points
- After replacement, kubectl vsphere login works without --insecure-skip-tls-verify on TCP/443 and TCP/6443
- MonitoringVCF Operations 8.16.1+ native integration monitors Supervisor and TKCs
Troubleshooting
Likely Panelist Questions
Q: Why NSX networking for the Supervisor and why Large Edge nodes?
DRI-TZU-CFG-005/006: VCF uses NSX for software-defined networking, and Large is the smallest Edge node size supported to activate a Supervisor; the cost is Edge capacity in the shared edge and workload cluster.
Q: How did you size the Supervisor and the address ranges?
DRI-TZU-CFG-004 small control plane (2000 pods) with DRI-TZU-NET-001..005: /24 overlay segment for the control plane, /20 pod and /22 service ranges behind NAT, and routable /24 ingress and egress ranges; resize per Table 121 (Medium 8 vCPU/24 GB/4000 pods) when needed.
Q: Who manages the life cycle?
DRI-TZU-LCM-001/002: the Supervisor through the vSphere Client and Tanzu Kubernetes clusters through kubectl; neither is integrated with SDDC Manager, which is a stated operational implication.
Q: How is access controlled?
DRI-TZU-SEC-001/002: Active Directory groups for DevOps administrators with Can Edit and for read-only users with Can View on each namespace; CA-signed SHA-2 certificate on the Supervisor API (SEC-003/004).
Failure Scenarios
Trade-off Analysis
Single-zone vs three-zone Supervisor
Chosen: Single-zone Supervisor (DRI-TZU-CFG-007)
Justification: A three-zone Supervisor needs three separate vSphere clusters; single-zone keeps the existing design and procedures unchanged.
Supervisor control plane size
Chosen: Small control plane nodes (DRI-TZU-CFG-004), resize later per Table 121
Justification: 2000 pods covers the design requirement with the smallest footprint; Medium/Large are available as scale-up.
Small TKC nodes vs larger nodes
Chosen: Small-size control plane and worker nodes, three of each (DRI-TZU-CFG-013..015)
Justification: Meets most scale requirements with high availability; larger nodes or additional clusters when scale demands.
Quiz — Developer Ready Infrastructure
- Extra Large
- Large
- Medium
- Small
- /16 VLAN-backed
- /28 overlay-backed NSX segment
- /24 overlay-backed NSX segment, routable
- /20 NAT subnet
- 2000
- 8000
- 1000
- 4000
- Harbor (image registry)
- Prometheus
- Grafana
- Jenkins
- vSphere Data Protection
- Commvault
- Velero + Velero plug-in for vSphere + Velero Data Manager
- Veeam
- Tanzu Mission Control
- VCF Operations
- vCenter Server (vSphere Client native workflows)
- SDDC Manager
- Additional NSX Edge node
- New VLAN
- Tier-1 Gateway with /28 overlay segment and IP pool
- Tier-0 Gateway
- /24
- /16
- /20
- /22
- vSphere Administrator
- DevOps Engineer
- Cloud Admin
- Auditor
- Service incoming pod traffic; instantiate additional /28 if IP space exhausts
- Host NSX Manager
- Connect to external corporate DNS
- Manage ESXi hosts
- SHA-1
- MD5
- SHA-2 or higher
- RIPEMD-160
- Replacing default self-signed cert with CA-signed cert on Supervisor K8s API endpoint
- Adjusting Supervisor size
- Installing Contour
- Setting VM Class to large
- 04
- 11
- 12
- 05
- PHP Guestbook with MongoDB
- Grafana
- Wordpress on TKC
- Bitnami Kubeapps
- Never
- When upgrading ESXi
- When adding an additional vSphere cluster as a new Supervisor
- Only in stretched deployments
Flashcards — Developer Ready Infrastructure
Labs
Lab 1: Enable a Supervisor on a VI Workload Domain
Configure prerequisites and activate a Small Supervisor (2000 pods) on the shared edge/workload cluster of a VI workload domain.
Starting State: VCF 5.2 with a VI workload domain; large-sized NSX Edge cluster deployed; AD over LDAP configured in vCenter; Microsoft CA available; DNS/NTP configured; subnets allocated (/24 mgmt, /20 pods, /22 services, /24 ingress, /24 egress).
- Confirm no manual content library is needed (VCF 5.0+: created automatically at Supervisor activation; VCF 4.5.2 and earlier: subscribed library in the shared edge and workload cluster per DRI-TZU-CFG-011)
- Create/verify Storage Policy 'vsphere-with-tanzu-storage-policy' (vSAN-backed)
- Open vSphere Client > Menu > Workload Management > Get Started > Add Cluster
- Select NSX networking; select large Edge cluster
- Configure Supervisor networking: mgmt /24, pod /20, service /22, ingress /24, egress /24
- Set control plane size to Small (4 vCPU / 16 GB per node)
- Assign storage policy; launch deployment
- Monitor progress to Ready state
- Create CSR for Supervisor API endpoint; sign via Microsoft CA; import cert (DRI-TZU-SEC-003)
- kubectl vsphere login --server <supervisor_ip> --vsphere-username administrator@vsphere.local
- Verify: kubectl get nodes; kubectl get namespaces
Lab 2: Deploy a Tanzu Kubernetes Cluster and Deploy Sample Application
Deploy a TKC in a vSphere namespace using the TKG Service and deploy the Wordpress blueprint via Helm.
Starting State: Supervisor from Lab 1 is Ready; AD security group gg-devops-engineers created and granted Can Edit on the namespace; kubectl context set to Supervisor.
- Create a vSphere namespace 'sfo-w01-ns01' in vSphere Client; assign storage policy and VM classes (guaranteed-medium)
- Grant Can Edit to gg-devops-engineers AD group on the namespace
- Apply TKC YAML using kubectl: kubectl apply -f sfo-w01-tkc01.yaml (version: v1.26.x, 3 control plane + 3 workers)
- Wait for TKC Ready: kubectl get tkc -n sfo-w01-ns01
- kubectl vsphere login --server <ip> --TanzuKubernetesCluster sfo-w01-tkc01 --TanzuKubernetesClusterNamespace sfo-w01-ns01
- kubectl config set-context sfo-w01-tkc01
- kubectl create namespace wordpress
- helm repo add bitnami https://charts.bitnami.com/bitnami; helm repo update
- helm install sfo-w01-tkc01-wp01 --namespace wordpress --set global.storageClass=vsphere-with-tanzu-storage-policy --set wordpressBlogName='Wordpress Instance' --set wordpressUsername=wp-admin --set wordpressPassword=<pw> bitnami/wordpress
- kubectl get svc -n wordpress sfo-w01-tkc01-wp01-wordpress (look up LoadBalancer external IP)
- Browse to LoadBalancer IP; verify Wordpress homepage loads
Lab 3: Configure Velero Backup and Restore for a TKC
Install Velero in a TKC, schedule daily backup to an S3-compatible object store, restore after simulated failure.
Starting State: TKC from Lab 2 deployed; MinIO or similar S3-compatible bucket available; Velero CLI on admin workstation.
- Install Velero plug-in for vSphere on Supervisor; install Velero Data Manager VM
- On TKC context: velero install --provider aws --plugins velero/velero-plugin-for-aws:v1.x --bucket tkc-backups --secret-file ./credentials-velero --use-volume-snapshots=false --backup-location-config region=minio,s3ForcePathStyle=true,s3Url=http://<minio>:9000
- velero schedule create daily-wordpress --schedule='0 2 * * *' --include-namespaces wordpress --ttl 168h
- Simulate failure: kubectl delete namespace wordpress
- velero restore create --from-schedule daily-wordpress
- Verify namespace and Wordpress resources restored
- Test data integrity by accessing Wordpress UI and verifying blog posts