In the two first posts of this series on Azure Arc-enabled VMware vSphere, we managed to extend Azure governance and management capabilities on VMware-based resources and to demonstrate the creation of a VMware virtual machine from the Azure portal.

If you missed on of the 2 firsts posts:

• Azure Arc-enabled VMware …

In the previous post (part 1), we covered the capabilities of Azure Arc-enabled VMware vSphere: a solution to extend Azure governance and management policies to VMware based workload.

We also deployed a Resource Bridge to establish the connection between a VMware environment and Azure. We can now explore vCenter …

Manage your VMware Datacenter through Azure Cloud tools

Announced in private preview stage during the Microsoft Ignite on November 2021, the Azure Arc integration with VMware vSphere is now available in public preview since March 31^th, 2022.

The feature, still in development process, is now labeled Azure Arc-enabled …

After a discovery of Azure VMware Solution REST API through the Postman collection in part 1, we will use some of the fundamentals API calls through az rest, a useful subset of the Azure Command-Line Interface.

Compared to Postman, I consider az rest an easier way to discover Azure REST API in a blog post as it doesn't …

Working on Azure VMware Solution since a couple of months now, I found very usefull to have a prepared list of API calls on a notebook or quick-reference document.

After a period of time, I did collect enought sample to consider doing a full Postman collection and by doing that, I was also considering to cover the …

This post is the second part of a small series about VMware Event Broker on Kubernetes with Knative functions.

If you plan to apply the following procedure, we assume that the content mentioned in the Part 1 is already deployed in your target setup.

Deploy VMware Event Broker with knative support

Disclaimer: This …

As mentioned in some previous posts (here or here), I do not deploy the instance-based packaging of the VMware Event Router: aka VEBA. I prefer to reuse existing Kubernetes cluster(s) to host the vmware event router and the associated functions.

Currently, most of my automation work relies on OpenFaaS® functions, and …

I recently made posts about the VMware Event Broker (aka VEBA) to explain basic on-boarding in the FaaS and Event-Driven worlds.

As you may have noticed, the FaaS concept is perfect for use-case where the automation will be:

• Stateless
• Fast running
• No latency sensitive
• Responsible of a single thing
• Deterministic

BTW, …

This post is a re-edition of a previous one: VMware Event Broker (aka VEBA) on Kubernetes – First steps, update to be applicable to the new 0.5.0 release of VEBA, including the support of helm chart deployment.

In the following post, we will (re)discover how to deploy the VMware Event Broker services (VEBA) within an …

The current post is a quickstart to VMware open-source project Container Service Extension (CSE), a Kubernetes as a Service for VMware vCloud Director.

The project is already well documented (CSE documentation) and you should not have any trouble to set it up by following the installation steps.

Except... if you plan …