Page tree


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 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) service. 

For more information about the Infoblox Grid and the DNS service, refer to the Infoblox NIOS documentationYou can deploy an Infoblox vNIOS for Red Hat OpenShift instance as a virtual member tied to an on-premise (non-cloud) NIOS Grid.

vNIOS Model for Red Hat OpenShift

Trinzic Series Virtual Appliance

Supported NIOS Versions

Overall Disk 

Number of 
CPU Cores


Supported as Grid Master 
and Grid Master Candidate

IB-V22258.5.3 and 8.5.4250864 GBNo

Known Limitations

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

  • vNIOS for Red Hat OpenShift supports only the IB-V2225 appliance.

  • In NIOS, the platform type for the vNIOS appliance is updated as KVM, as seen on the Grid tab -> Grid Manager tab -> Members tab of Grid Manager.
  • HA and LAN2 interfaces are not supported.
  • DHCP and IPv6 configurations are not supported.
  • Subscriber Service Provider features that include (but not limited to) virtual DNS Cache Acceleration, Advanced DNS Protection software (virtual Advanced DNS Protection), Subscriber Secure Policy, and Parental Control Policy are 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.
  • No labels

This page has no comments.