Skip to content
This repository has been archived by the owner on Mar 27, 2023. It is now read-only.

Latest commit

 

History

History
28 lines (17 loc) · 1.1 KB

GETTING-STARTED.md

File metadata and controls

28 lines (17 loc) · 1.1 KB
Raw

Get Started with vm-operator-api

This guide will walk you through the process of integrating vm-operator-api into your project

Prerequisites

The vm-operator-api project currently requires a ESXi cluster in vSphere 7 with Kubernetes.

What this means in functional terms is that you can manage workloads in a given Workload Namespace using a Kubernetes client connected directly to the an embedded Kubernetes API Server running in the vSphere cluster. With the correct privileges, you can create CRD objects in your vSphere cluster which are reconciled into vSphere objects - everything from a single VM (VirtualMachine) to a full virtualized Kubernetes Cluster (TanzuKubernetesCluster)

The vm-operator-api APIs currently allow you to monitor VirtualMachine objects that exist in the target namespace and before long, it will also allow you to create and manage them.

Step 1: Verify client access

Check your client access by viewing VirtualMachines in the target cluster

kubectl get VirtualMachines --all

Step 2: Build and Test the sample code

cd hack/samples
make all
bin/list-ctrl