Supported platforms
ZWAF VE on Red Hat OpenShift Virtualization
ZWAF VE runs as a virtual machine in your OpenShift cluster, next to the applications it protects, with the same features as the ZWAF R28 appliance (WAF, load balancing, bot protection, access control), installed with oc and virtctl from a qcow2 image.
ZWAF is Red Hat Partner Validated for OpenShift Virtualization. ZWAF in the Red Hat Ecosystem Catalog
What you get
ZWAF where your applications now run
The virtual edition is the same software as the appliance, with every feature of your edition. On OpenShift Virtualization it is one more virtual machine in the cluster you already run.
It moves with your applications
When your applications move from VMware to OpenShift Virtualization, ZWAF moves with them, and so does your ZWAF VE licence, at no cost: you get one extra licence move for the migration. No VMware cluster stays behind just for the WAF and the load balancer.
Created with the tools you already use
ZWAF VE is an ordinary VirtualMachine resource in your cluster. You create it with oc and virtctl or from the web console, from a qcow2 disk image imported into a DataVolume.
On your own networks
The management port and the traffic ports sit on bridged networks. ZWAF's addresses are on your networks directly, not on the pod network.
Its security comes along
A persistent virtual TPM opens ZWAF's encrypted data partition and binds the licence to the machine. ZWAF enrolls its own Secure Boot keys at its first start and keeps them in the machine's persistent UEFI variables.
It is licensed by edition and capacity tier, as a subscription. We support ZWAF on OpenShift Virtualization. For OpenShift, Red Hat supports you under the subscription you have with them.
Before you start
What it needs
Set these up in the cluster before you create the virtual machine.
- Red Hat OpenShift 4.22 or 5.0, with OpenShift Virtualization of the same version
- A storage class for the virtual machines' state, named in the HyperConverged resource (
spec.storage.vmStateStorageClass) before the machine is created. ZWAF keeps its UEFI variables and its persistent virtual TPM there. - A Linux bridge on the node for each network (an NMState NodeNetworkConfigurationPolicy) and a
cnv-bridgeNetworkAttachmentDefinition for each: one for management, one or more for application traffic. - At least 4 vCPUs and 8 GB of memory for each instance, more for the higher capacity tiers
- A disk of at least 32 GB; 480 GB for production
- The disk image
zwaf_<version>.qcow2from the Software page of the ZWAF Cloud portal. Check its SHA-256 against the value published there.
Installation
From the disk image to the first sign-in
Four steps, from a workstation with oc and virtctl logged in to the cluster.
Upload the disk image
Upload the qcow2 into a DataVolume. The size you give here becomes the size of the virtual machine's disk.
virtctl image-upload dv zwaf-ve-system -n <namespace> --size=480Gi \ --image-path=zwaf_<version>.qcow2 --storage-class=<storage class> \ --access-mode=ReadWriteOnce- If your storage class binds volumes in
WaitForFirstConsumermode (LVM Storage, for example), add--force-bind.
- If your storage class binds volumes in
Create the virtual machine
Save this manifest with your own name, namespace, serial number and network names, and apply it with
oc apply -f zwaf-ve.yaml.apiVersion: kubevirt.io/v1 kind: VirtualMachine metadata: name: zwaf-ve namespace: <namespace> spec: runStrategy: Always template: spec: domain: cpu: cores: 4 memory: guest: 8Gi firmware: serial: <appliance serial> bootloader: efi: secureBoot: false persistent: true devices: tpm: persistent: true disks: - name: system disk: bus: virtio interfaces: - name: mgmt bridge: {} model: virtio - name: data1 bridge: {} model: virtio - name: data2 bridge: {} model: virtio autoattachSerialConsole: true networks: - name: mgmt multus: networkName: <management NAD> - name: data1 multus: networkName: <first traffic NAD> - name: data2 multus: networkName: <second traffic NAD> volumes: - name: system dataVolume: name: zwaf-ve-systemfirmware.serialis the appliance's serial number: the licence is bound to it and to the virtual TPM.- Leave
secureBoot: false. The firmware then starts with an empty key store, ZWAF enrolls its own Secure Boot keys at its first start, and from then on Secure Boot is enforced.persistent: truekeeps those keys. tpm.persistent: truekeeps the virtual TPM from one start to the next, so ZWAF opens its data partition every time.- The first interface is the management port; the next ones carry traffic.
Set it up on the serial console
The machine starts at once. Open its serial console from the Console tab of the virtual machine, or with the command below. ZWAF asks for the management address, the gateway, DNS and NTP, shows the recovery key of its encrypted data partition once and creates the first administrator. Then sign in at
https://<management-address>/: the first sign-in sets a new password and a second factor (TOTP).virtctl console zwaf-ve -n <namespace>Activate the licence and keep ZWAF up to date
Activate the licence under System > Licence, online through ZWAF Cloud or with a licence file. Updates install from the web interface, from ZWAF Cloud or from a signed update file.
Edit the VirtualMachine in place; do not delete and recreate it. Deleting it also deletes its UEFI variables and virtual TPM, and a new machine on the same disk cannot open the data partition: you would have to restore ZWAF from a backup.
Next step
See ZWAF in front of your applications
Tell us what you run and how your traffic looks. We will show you how ZWAF would protect it and answer your questions about licensing and support. Resellers and integrators are welcome too: we are building our partner network and would like to hear from you.