Page tree

Contents

Before deployment, consider the following requirements:
  • Customer-provided bare-metal systems running Linux and Docker version 19.03.5 and above.
  • The minimum supported Docker version is 19.03.5.
  • Non-standard paths to the Docker daemon socket, such as during Docker installation with Snap, are not supported.
  • Kubernetes is not supported.
  • VMs deployed on VMware ESXi servers:
    • For regular OVA deployment, supported VMware ESXi server versions are 6.0, 6.7, and 7.0.
    • For high capacity OVA, deployment, supported VMware ESXi serves version 6.5 and above.

For information on how to download OVA packages, see Downloading BloxOne Apps.

  • VM infrastructures such as Hyper-V or KVM, running Linux and Docker version 19.03.5 or above. For information about the supported Linux VMs for Hyper-V, refer to this article.
  • Dind (Docker-in-Docker) configuration is not supported for on-prem host deployments.
  • Infoblox supports deploying on-prem hosts using KVM hypervisor on bare-metal appliances.
  • Infoblox supports all versions of OpenStack for deploying on-prem hosts using OpenStack with KVM hypervisor.
  • It is highly recommended that you adhere to the minimum hardware and platform requirements for on-prem hosts. DHCP version 3.1 or higher is required for DHCP clustering (Advanced Active-Passive). If you do not follow the minimum hardware and platform requirements for on-prem hosts, DHCP clustering will not be supported. For more information about DHCP clustering, see Creating HA Groups.

Note

Dind (Docker-in-Docker) configuration is not supported for on-prem host deployments.

Infoblox has validated the following platforms:

  • Red Hat Enterprise Linux 7.8
  • CentOS 7.8
  • Ubuntu: For new deployments, Infoblox recommends Ubuntu 18.04 while we continue to support Ubuntu16.04 for existing deployments.
  • OpenStack 5.6.0 with nova-manage 24.1.0
  • QEMU emulator version 4.2.1 (Debian 1:4.2-3 Ubuntu 6.17)

For bare-metal configuration, ensure that the following requirements are in place:

  • Avoid CIDR overlapping with the default CIDR.
  • No K3s binary should be placed in this directory: /usr/local/bin/.
  • SELinux policy is properly set up.

Note

For k3s to be successfully installed on a Red Hat and CentOS based bare-metal on-prem host, use the following command to install the required package:

yum install -y container-selinux selinux-policy-base
rpm -i https://rpm.rancher.io/k3s-selinux-0.1.1-rc1.el7.noarch.rpm

After you install the required package, complete the following:

  1. Disable the firewall service.
  2. Enable the iptables service (if it exists).
  3. Reboot the system.

  • No labels

This page has no comments.