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 started my journey to the Kubernetes world, switching from theory knowledge to practical use-cases for customers.

This is a wonderful new technical area to discover with a lot of new:

• Tools
• Features/Capabilities
• Documenations
• Communities
• Best-practices
• …

Of course, I am far-far-away to master those new …

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 …

Warning: Since the publication of VEBA 0.5.0, the development team provides a helm chart deployment method. According to this, I made a re-edition of this post to provide a new setup workflow: VMware Event Broker 0.5.0 (aka VEBA) on Kubernetes – First steps

In the following post, we will discover how to deploy the …