WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud
  • Tanzu
    • Application Modernization
    • Tanzu services
    • Tanzu Community Edition
    • Tanzu Kubernetes Grid
    • vSphere with Tanzu
  • Home Lab
  • Nested Virtualization
  • Apple

Integrating VMware Event Broker Appliance (VEBA) with Zapier

04.28.2022 by William Lam // Leave a Comment

Michael Gasch and I recently had an internal discussion with an Engineer about our VMware Event Broker Appliance (VEBA) project and they had shared some additional integration ideas that could be useful for our community. The solution was a cloud service called Zapier, that makes it easy for users (non-developers) to automate workflows across a number of web applications. In the case of Zapier, they have a catalog of over 4k+ integrations and users can also create their integration into Zapier by creating what they call a Zap.

The really cool thing about a Zap is that it can be trigged via an incoming webhook! Why is that cool, well you can probably guess from the title of this article? 😀

Simliar to how VEBA can easily send a notification to Slack or Microsoft Teams via a webhook, VEBA can also be used to integrate with over 4k+ apps within Zapier using this exact same pattern. In fact, the code to trigger a Zapier workflow within a VEBA function is exactly the same and it was literally copy/paste, which took me less than 5 minutes to fully implement!

The use case that I thought would be cool to demonstrate with Zapier is to react to all failed vCenter Server login attempts and automatically send that information to a Google Spreadsheet as shown in the final implementation below.


A huge benefit of using a solution like Zapier is that it simplifies the more complex integrations. One example is if you wish to integrate with Google Docs, you will need to figure out the authentication scheme and understand the required Google APIs and the finally write the code to perform the task you are interested in. With Zapier and simliar solutions, all of that is automatically handled for you and requires very little configuration, which can all be setup using the Zapier UI.

If you are interested in using Zapier or implement the solution above, take a look at the instructions below.

[Read more...]

Categories // VMware Cloud on AWS, vSphere Tags // VMware Event Broker Appliance, Zapier

How to configure Knative and containerd in VMware Event Broker Appliance (VEBA) to use a private registry?

03.29.2022 by William Lam // 1 Comment

I was recently helping out fellow colleague Patrick Kremer who was looking into an issue that one of our users had filed on how to configure the VMware Event Broker Appliance (VEBA) so that it can take advantage of a custom container registry for deploying VEBA functions. If you attempt to specify a container image from a private container registry, especially one that has a self-signed certificate, you will see the following error:

Unable to fetch image "harbor.primp-industries.local/library/veba/kn-py-echo:1.0": failed to resolve image to digest: Get "https://harbor.primp-industries.local/v2/": x509: certificate signed by unknown authority; Get "https://harbor.primp-industries.local:443/v2/": x509: certificate signed by unknown authority

I had assumed that this should have been a pretty trivial configuration change to make the underlying Kubernetes container runtime trust the desired container registry and that there would be an easy to follow tutorial that Patrick could search for. The latest release of VEBA has moved away from using the Docker runtime to containerd and this should have helped narrow down the search results, at least that was our assumption.

Not only are there plenty of resources online, but there seem to be multiple methods depending on the version of Kubernetes and containerd which was pretty overwhelming. After several attempts using various blog articles, Patrick found that the trust error has still not gone away. I finally decided to take a closer look and discovered that there are actually two components that must be updated to properly support a private container registry: containerd & Knative Serving Controller. I eventually found this page in the Knative Serving documentation that provided a hint but ultimately, I was not able to fully grok the details until I came across this Github thread that brought clarity on how to create the required secret for the root CA certificate which would allow the Knative Serving controller to trust the root CA certificate.

Below are the instructions for the required changes and I have also attempted to simplify the steps by providing automation snippets that makes it easy for anyone to consume. In my setup, I am using Harbor registry which was built from my Harbor Virtual Appliance but the steps should apply for any other private container registry.

[Read more...]

Categories // Cloud Native, Kubernetes Tags // Cloud Native Runtime, Harbor, Knative, VMware Event Broker Appliance

VMware Event Broker Appliance (VEBA) v0.7.2

03.09.2022 by William Lam // Leave a Comment

The VEBA team is excited to share that we have just published our v0.7.2 release, which is a minor release and contains a number of enhancements as well as fixes that our users had observed in earlier v0.7.x releases. Highlighted below are some of new user facing capabilities along few of the backend updates. For a detailed change log, please refer to the v0.7.2 release notes.

What's New:

  • 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 (here and here) 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 Fixes

Backend Updates:

  • Updated OS to latest Photon OS 4.0 Rev2
  • Updated Knative Serving/Eventing stack to v1.1.0
  • Updated Kubernetes to v1.21.5
  • Migrated container runtime from Docker to Containerd
  • Pipeline and automation overhaul, publishing artifacts to GCR for scale and address docker rate limit issues

Categories // Automation, vSphere Tags // VMware Event Broker Appliance

  • « Previous Page
  • 1
  • 2
  • 3
  • 4
  • …
  • 10
  • Next Page »

Search

Author

William Lam is a Senior Staff Solution Architect working in the VMware Cloud team within the Cloud Infrastructure Business Group (CIBG) at VMware. He focuses on Cloud Native technologies, Automation, Integration and Operation for the VMware Cloud based Software Defined Datacenters (SDDC)

Connect

  • Email
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • Vimeo

Recent

  • Automated ESXi Installation with a USB Network Adapter using Kickstart 02/01/2023
  • How to bootstrap ESXi compute only node and connect to vSAN HCI Mesh? 01/31/2023
  • Quick Tip - Easily move or copy VMs between two Free ESXi hosts? 01/30/2023
  • vSphere with Tanzu using Intel Arc GPU 01/26/2023
  • Quick Tip - Automating allowed and not allowed Datastores for use with vSphere Cluster Services (vCLS) 01/25/2023

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2023

 

Loading Comments...