Prerequisites

Last published : Aug 25, 2026
  1. Be ready with the following information -
    • Names of all the nodes.
      Note: Runkubectl get nodes -o wideon the master node to obtain Names and IP addresses of the nodes.
Use NAME and INTERNAL-IP from the output similar to the following -
NAME     STATUS ROLES  AGE VERSION         INTERNAL-IP
k8s-cp-1.lab.k8s.lan Ready  master 75d v1.20.0+558d959 192.168.22.201
k8s-cp-2.lab.k8s.lan Ready  master 75d v1.20.0+558d959 192.168.22.202
k8s-cp-3.lab.k8s.lan Ready  master 75d v1.20.0+558d959 192.168.22.203
k8s-w-1.lab.k8s.lan  Ready  worker 75d v1.20.0+558d959 192.168.22.211
  • Operating system hardware path of the disks which are being managed by other storage vendors that need to be excluded from InfoScale disk group.
  • Optionally if you want to exclude boot disks, device path to the boot disks.
    Note: Arctera recommends excluding boot disks.
  • Custom Registry address to set up registry where InfoScale images are pushed.
  1. Before deploying the product, verify that the RKE2 (Rancher Kubernetes Engine 2) cluster is installed, configured, and running with Rancher. This ensures that the Kubernetes cluster is prepared to support the application deployment.
  2. Ensure that all nodes are synchronized with the NTP Server.
  3. Reserve network ports for exclusive use of InfoScale as under -
    Component Port
    LLT over UDP Serially onwards 50000 (as many as configured LLT links)
    VVR (Needed only if you want to configure DR) 4145 (UDP), 8199 (TCP), 8989 (TCP)
  4. Add local or shared storage to all the worker nodes before you proceed with the deployment.
  5. Ensure that stale InfoScale kernel modules (vxio,vxdmp,veki,vxspec,vxfs,odm,glm,gms) from previous installation do not exist on any of the worker nodes.
    Note: You can reboot a worker node to unload all stale InfoScale kernel modules.
  6. Hostnames of the InfoScale nodes must exactly match with the fully qualified domain names(FQDN) of the RKE2 nodes.
  7. SE Linux is disabled on all the nodes
  8. RKE2 cluster must be configured by using IPv4 only.
  9. Optionally, add custom ciphers to kube-apiserver. Refer to RKE2 documentation to know how to add ciphers.
  10. git must be installed on the master node.