Prerequisites checklist

Before installing ITRS Analytics, ensure that all the prerequisites are met in the environment where you will deploy.

Online Bring-Your-Own (BYO) cluster installation Copied

• Make sure that your Kubernetes version is compatible with the ITRS Analytics Platform. Supported managed service providers are listed below.

  Expand table

  Kubernetes version	1.27	1.28	1.29	1.30
  vSphere with Tanzu	✓	✓	✓
  Azure AKS			✓	✓
  Amazon EKS	✓	✓	✓	✓
  Openshift	✓	✓	✓	✓
  Google Kubernetes Engine (GKE)				✓

• Check that resource and hardware requirements are met.

• Note the host name of the server, which will be used for accessing ITRS Analytics from outside the Kubernetes cluster.

• Make sure that you have host names for accessing ITRS Analytics from outside the Kubernetes cluster. These host names must be mapped to the corresponding Kubernetes services that will be created during installation.

  • Web UI: for example obcerv.mydomain.internal.
  • Data ingestion: to publish from Geneos Gateways; for example obcerv-ingestion.mydomain.internal.

• Make sure that a load balancer is configured for your cluster.

• Check that cluster permissions are set. Cluster role configs are required on a BYO cluster. You can also opt to grant minimal RBAC permissions to KOTS.

Air-gapped Bring-Your-Own (BYO) cluster installation Copied

• Make sure that your Kubernetes version is compatible with the ITRS Analytics Platform. Supported managed service providers are listed below.

  Expand table

  Kubernetes version	1.27	1.28	1.29	1.30
  vSphere with Tanzu	✓	✓	✓
  Amazon EKS	✓	✓	✓	✓
  Openshift	✓	✓	✓	✓
  Google Kubernetes Engine (GKE)				✓

• Check that resource and hardware requirements are met.

• Provide access to a Docker registry to pull and push container images. The host name must support Docker v2 protocol.

• Note the host name of the server, which will be used for accessing ITRS Analytics from outside the Kubernetes cluster.

• Make sure that you have host names for accessing ITRS Analytics from outside the Kubernetes cluster. These host names must be mapped to the corresponding Kubernetes services that will be created during installation.

  • Web UI: for example obcerv.mydomain.internal.
  • Data ingestion: to publish from Geneos Gateways; for example obcerv-ingestion.mydomain.internal.

• Make sure that a load balancer is configured for your cluster.

• Check that cluster permissions are set. Cluster role configs are required on a BYO cluster. You can also opt to grant minimal RBAC permissions to KOTS.

• Before installing, you can deploy and scan ITRS Docker images. Refer to this sample list of images from the Docker registry

• Make sure that you are not using ARM64 processors, which is currently not supported in airgap installations.

Online embedded cluster installation Copied

Important

Embedded clusters are currently not fit for production use due to the following limitations:

• High availability (HA) of the cluster’s control plane is still in the alpha stage.
• PersistentVolumeClaim (PVC) in a multi-node cluster are not highly available. ITRS Analytics requires them to be.

These limitations are currently being addressed to improve the embedded cluster.

• Check that resource and hardware requirements are met.

• Note the host name of the server, which will be used for accessing ITRS Analytics from outside the Kubernetes cluster.

• Check that cluster permissions are set. You need to use sudo to access the cluster.

• Make sure that the server has a file descriptor limit of at least 1024 for fs.inotify.max_user_instances.

Air-gapped embedded cluster installation Copied

Important

Embedded clusters are currently not fit for production use due to the following limitations:

• High availability (HA) of the cluster’s control plane is still in the alpha stage.
• PersistentVolumeClaim (PVC) in a multi-node cluster are not highly available. ITRS Analytics requires them to be.

These limitations are currently being addressed to improve the embedded cluster.

• Check that resource and hardware requirements are met.

• Note the host name of the server, which will be used for accessing ITRS Analytics from outside the Kubernetes cluster.

• Make sure that you have host names for accessing ITRS Analytics from outside the Kubernetes cluster. These host names must be mapped to the corresponding Kubernetes services that will be created during installation.

  • Web UI: for example obcerv.mydomain.internal.
  • Data ingestion: to publish from Geneos Gateways; for example obcerv-ingestion.mydomain.internal.

• Check that cluster permissions are set. You need to use sudo to access the cluster.

• Make sure that you are not using ARM64 processors, which is currently not supported in airgap installations.

• Make sure that the server has a file descriptor limit of at least 1024 for fs.inotify.max_user_instances.