Infoblox vNIOS for Red Hat OpenShift is a virtual appliance designed for deployment on Red Hat^® OpenShift^®, an enterprise-ready Kubernetes container platform. The virtual appliance enables you to deploy large, high-performance, robust, manageable, and cost-effective Infoblox Grids.

The supported Infoblox DDI (Domain Name System, Dynamic Host Control Protocol and IP Address Management) virtual appliances listed in below tables enable you to deploy large, high-performance, robust, manageable, and cost-effective Infoblox Grids. Yo
u can deploy Infoblox vNIOS for Red Hat OpenShift instances as a Grid Manager, Grid Manager Candidate, and/or a member for installer-provisioned infrastructure (IPI), user-provisioned infrastructure (UPI), or single-node OpenShift (SNO) on Intel based X86-64 ‘bare metal’ platforms with the default OVN/OVS CNI or certain SR-IOV based networking for high rate environments.

The NIOS virtual appliance for Red Hat OpenShift functions as a virtual machine running on KubeVirt virtualization. It provides integrated, secure, and easy-to-manage DNS (Domain Name System), DHCP (Dynamic Host Control Protocol), and IPAM (IP Address Management) services. For more information about the Infoblox Grid, DNS, DHCP, and IPAM services, refer to the Infoblox NIOS documentation.

The performance of a vNOIS VM instance deployed on a Red Hat OpenShift host is impacted by the huge page sizes configured on the instance and on the host, and also by the services enabled on the instance.
Although, huge page sizes configured on the host and the VM instance are independent of each other, the following behavior is observed:

• When the host is configured to allocate huge pages to the instance, performance issues are reduced as it minimizes disk fragmentation, which otherwise has a significant impact on the performance. However, if the host is over provisioned with VM instances, performance of the VM will be impacted. To avoid it, refer to the best practices recommended by the Hypervisor.

• When the host is not configured to allocate huge pages to the instance, performance issues can elevate due to increased possibility of disk fragmentation, which often leads to non-contiguous physical memory blocks being allocated to the VM. In some cases, this may also lead to memory allocation failures.

Trinzic Appliances

Supported Trinzic X5 appliance models for vNIOS for Red Hat OpenShift

Supported Trinzic X6 appliance models for vNIOS for Red Hat OpenShift

* If a vNIOS instance is running on a NIOS version prior to 9.0.1, the disk size will be set to 250 GB.

IB-FLEX Appliances

The following table lists the vNIOS for Red Hat OpenShift IB-FLEX models supported from NIOS 9.4.0 and later releases. For more information about IB-FLEX, see Infoblox NIOS Documentation.

Known Limitations

The known limitations of vNIOS for Red Hat OpenShift are as follows:

• In NIOS version 8.5.3, 8.5.4, and 8.6.1, the platform type for the vNIOS appliance is updated as KVM.

• LAN2 interface is not supported.

• Microsoft Management and the Security Ecosystem features have not been qualified for the current release and are not supported.

• If you need to shut down a vNIOS for Red Hat OpenShift instance, shut it down from the Red Hat OpenShift web console.
  If you perform the shutdown operation from Grid Manager, the instance is restarted because the state of the VM instance is controlled by the virtual machine deployer state controller, and any change in the state that is not caused by the controller is considered a conflict.

• You may observe occasional performance drops when you run DNS tests such as negative query and delegated zone referrals on IB-V4015 appliances.

• Unexpected issues may occur if you add a static IP address over an existing dynamic IP address in an vNIOS for Red Hat OpenShift instance.