Deploy VMware Event Broker Appliance with Knative
Customers looking to seamlessly extend their vCenter by either deploying our prebuilt functions or writing your own functions can get started quickly by deploying VMware Event Broker Appliance with Knative as the Event Processor
Appliance Deployment Steps
- 4 vCPU and 8GB of memory for VMware Event Broker Appliance
- vCenter Server 6.x or greater
- The VEBA UI requires vCenter Server 7.0 or greater
- vCenter TCP/443 accessible from Appliance IP address
- Account to login to vCenter Server (readOnly is sufficient)
Download the VMware Event Broker Appliance (OVA) from the VMware Fling site.
Deploy the VMware Event Broker Appliance OVA to your vCenter Server using the vSphere HTML5 Client. As part of the deployment you will be prompted to provide the following input:
- Hostname - The FQDN of the VMware Event Broker Appliance. If you do not have DNS in your environment, make sure the hostname provide is resolvable from your desktop which may require you to manually add a hosts entry. Proper DNS resolution is recommended
- IP Address - The IP Address of the VMware Event Broker Appliance
- Network Prefix - Network CIDR Selection (e.g. 24 = 255.255.255.0)
- Gateway - The Network Gateway address
- DNS - DNS Server(s) that will be able to resolve to external sites such as Github for initial configuration. If you have multiple DNS Servers, input needs to be space separated.
- DNS Domain - The DNS domain of your network
- NTP Server - NTP Server(s) for proper time synchronization. If you have multiple NTP Servers, input needs to be space separated.
Proxy Settings (Optional)
- HTTP Proxy Server - HTTP Proxy Server followed by the port (e.g. http://proxy.provider.com:3128)
- HTTPS Proxy - HTTPS Proxy Server followed by the port (e.g. http(s)://proxy.provider.com:3128)
- Proxy Username - Optional Username for Proxy Server
- Proxy Password - Optional Password for Proxy Server
- No Proxy - Exclude internal domain suffix. Comma separated (localhost, 127.0.0.1, domain.local)
OS Credentials (Required)
- Root Password - This is the OS root password for the VMware Event Broker Appliance
- Enable SSH - Check the box to allow SSH to the Appliance (SSH to the appliance is disabled by default)
- vCenter Server - This FQDN or IP Address of your vCenter Server that you wish to associate this VMware Event Broker Appliance to for Event subscription
- vCenter Username - The username to login to vCenter Server, as mentioned earlier, readOnly account is sufficient
- vCenter Password - The password to the vCenter Username
- vCenter Username to register VEBA UI (Optional) - Username to register VMware Event Broker UI to vCenter Server for Knative Processor
- vCenter Password to register VEBA UI (Optional) - Password to register VMware Event Broker UI to vCenter Server for Knative Processor
- Disable vCenter Server TLS Verification - If you have a self-signed SSL Certificate, you will need to check this box
Note: The minimum vSphere Privileges that is required for proper VEBA UI functionality are: Register Extension, Update Extension (Installing Plugins) and Manage Plugins (Updating Plugins)
Event Processor Configuration (Required)
- Event Processor - Choose Knative
Note: Selecting Knative here will default to using the Embedded Knative deployment within the VMware Event Broker Appliance. If this is your intent, you do not have to fill in any of the settings for the Knative Configuration section below. The Knative Configuration section below is for use with an External Knative installation.
Existing Knative Environment Configuration (Optional)
If you do want the Embedded Knative deployment in the VMware Event Broker Appliance and you have your own External Knative installation, the following settings are required.
- Host - Knative host (e.g. mybroker.corp.local:8080)
host field blank to automatically enable the embedded Knative broker
- Scheme - HTTP or HTTPS protocol the broker is using
- Disable Knative host TLS Verification - Only applicable for HTTPs scheme. If you have a self-signed SSL Certificate, you will need to check this box.
- Path - Additional path to append to the host if required, e.g. “/default/broker”
For more information on using the Knative Processor, please take a look at the VMware Event Router documentation
- Debugging - When enabled, this will output a more verbose log file that can be used to troubleshoot failed deployments
- POD CIDR Network - Customize POD CIDR Network (Default 10.99.0.0/20). Must not overlap with the appliance IP address
Power On the VMware Event Broker Appliance after successful deployment. Depending on your external network connectivity, it can take a few minutes while the system is being setup. You can open the VM Console to view the progress. Once everything is completed, you should see an updated login banner for the various endpoints:
Appliance Status: https://[hostname]/status
Install Logs: https://[hostname]/bootstrap
Appliance Statistics: https://[hostname]/stats
NOTE: If you enable Debugging, the install logs endpoint will automatically contain the more verbose log entries.
You can verify that everything was deployed correctly by opening a web browser and accessing one of the endpoints along with the associated admin password you had specified as part of the OVA deployment.
Deploy a Function
At this point, you have successfully deployed the VMware Event Broker Appliance and you are ready to start deploying your functions!