Evolution of VEBA

VEBA v0.8.0

Features

• Software Build-of-Material (SBOM) updated. See Release Notes for detailed Version changes

• Replaced VMware Event Router with VMware Tanzu Sources for Knative

• All VEBA endpoints now protected with basic authentication

• New Google Chat notification function

• Migrated function container images from Google (GCR) to Github (GHCR)

• Updated all Powershell/PowerCLI functions with the latest PS/PCLI base images

• Improved website documentation

• Various Bug Fixes and Code Improvements

VEBA v0.7.5

Features

• Software Build-of-Material (SBOM) updated. See Release Notes for detailed Version changes

• Converted Virtual Appliance Packer format from JSON to HashiCorp Configuration Language (HCL)

• Various Documentation Updates & Bug Fixes

VEBA v0.7.4

Features

• Fixed VEBA vSphere UI for subscribing to multiple events for single function

VEBA v0.7.3

Features

• New VMware Harbor, Zapier, NSX Tag Sync & Unapproved Portgroup Usage Functions

• Ported Datastore Usage Email, vSphere HA Restart & Host Maint. Alarm functions to Knative

• Enhanced pattern matching for EventBridge processor

• Various Documentation Updates & Bug Fixes

VEBA v0.7.2

Features

• New Knative PowerCLI template (quickly get started on building new functions)

• PowerShell Slack Function enhancement to be event agnostic + customizable message

• New PowerCLI example function to enforce VDS & DVPortgroup configs

• Syslog now captures all logs via Fluentbit

• RabbitMQ (triggers) now supports function scaling to scale out when there’s a burst of events

• Added Let’s Encrypt documentation

• Various backend updates (see this blog post for more details)

VEBA v0.7.1

Features

• Fix special character handling for VEBA vSphere UI plugin

• Fix imagePullPolicy for knative-contour in air-gap deployment

• Improved website documentation

• More Knative Function Examples

VEBA v0.7.0

Features

• New VMware Horizon Event Provider

• New Generic Webhook Event Provider

• Embedded cAdvisor for Monitoring

• Support for External Syslog

• Lots of new Knative PowerShell & PowerCLI Function Examples

• Deprecation of OpenFaaS & EventBridge Event Processors

VEBA v0.6.1

Features

• Knative PowerShell / PowerCLI Base Container Image Templates

• New Knative PowerCLI, Python and Go Function Examples

• Custom TLS Certificate support

• Documentation for adding Trusted Root Certificate to VEBA

• Helm support for Knative

• Enhanced Release Notes

VEBA v0.6.0

Features

• Embedded Knative (new default Event Processor)​

• vSphere UI integration (H5 Client Plugin)​

• 1st class PowerShell Support in Knative​

• Easy vSphere CloudEvents Viewer (Sockeye)

VEBA v0.5.0

Features

• Helm chart for simplified deployment experience

• Introduced support for external Knative environment​ as the Event Processor

• Implement at-least-once delivery semantics and improve resiliency across all processors

• Contributions back to Knative and govmomi for better vSphere eventing integration

VEBA v0.4.0

Features

• Introduced Otto

• Launched vmweventbroker.io

• Easier deployment of router in a Kubernetes environment (non-appliance mode) → towards core vSphere integration (e.g. WCP)

• Introduced DCUI with several EasterEggs

VEBA v0.3.0

Features

• Introduced VMware Event Router

• Added support for AWS EventBridge as an Event Processor

• Conformance with CloudEvents

• Support all vCenter events (incl. full payload)

• Improved contribution guidelines due to high interest in contributing to VEBA from customers/partners

• Add more enterprise features, e.g. logging and metrics

VEBA v0.2.0

Features

• Added more enterprise details, e.g. proxy support, offline deployments

• Documentation improvements and more samples from the community

Launching VEBA v0.1.0

VEBA Fling v0.1.0 released live at VMworld Europe - ‘Do it, do it, do it' chants when @embano1 and @lamw ask if they should release the vCenter Event Broker Appliance fling (powered by @openfaas) live during their session!

Features

• Introduced VEBA v0.1.0 with OpenFaaS as the default Event Processor​ and vCenter as the Event Provider