3V0-21.25 Advanced VMware Cloud Foundation 9.0 Automation

In VCF 9.0 Automation, a Day 2 Operation is an extension of the platform ' s native capabilities, allowing users to perform lifecycle tasks on already deployed resources. To enable a vMotion migration through the automation portal, the administrator must first Create a resource action . This construct defines the UI element that will appear when a user selects a VM in their deployment list. The resource action must then be mapped to an execution logic; the most efficient and verified method is to Call the pre-defined Orchestrator workflow named Migrate virtual machine with vMotion . This workflow is part of the standard vCenter integration library in VCF Operations Orchestrator and contains all the necessary logic to handle destination host selection and validation. Once the action is created and mapped to the workflow, it must be added to a Service Broker Policy to entitle the appropriate users or projects to perform the migration task.

Velero is the industry-standard and VMware-supported service integrated into VCF 9.0 for the backup and restoration of Kubernetes-based workloads, specifically vSphere Pods and persistent volumes. Within the VCF Automation framework, Velero is often deployed as part of the Supervisor services or within TKG clusters to provide data protection for stateful applications. It captures the state of the Kubernetes API objects (such as Pod specs and Secrets) and triggers snapshots of the underlying vSphere storage (via the Cloud Native Storage/CNS driver) to ensure that workloads can be recovered in the event of a cluster failure or accidental deletion. While other services like ArgoCD handle continuous delivery and VKS handles cluster lifecycle, only Velero is dedicated to the operational task of disaster recovery and migration of containerized resources within the vSphere Supervisor environment.