Deployment options
Before you install ITRS Analytics, choose a deployment for your organization. The deployment you choose determines who operates the platform, where it can run, and which install path to follow. Compare the deployments on this page, then follow the install path that matches your organization.
| Deployment | Where it runs | Who administers it | When to choose |
|---|---|---|---|
| ITRS Managed | An AWS VPC hosted by ITRS, or your organization’s VPC with ITRS operating the instance | ITRS and the hyperscaler | Your organization permits a managed (SaaS) solution, and data residency requirements can be met. |
| Client-managed cluster | Your organization’s hyperscaler Kubernetes cluster (EKS, GKE, or AKS) | Your organization and the hyperscaler | Your organization must self-host, and Kubernetes is already part of your platform strategy. Also known as Bring-Your-Own (BYO) cluster. |
| Application on VM | Hyperscaler VMs or self-hosted VMs | Your organization. Cluster issues in the bundled Kubernetes layer are escalated to ITRS. | Your organization must self-host, Kubernetes expertise is limited, and your team needs a simpler install with self-hosted control. Uses Embedded Cluster. |
ITRS Managed Copied
Choose ITRS Managed when ITRS should operate ITRS Analytics and your team should not install or manage Kubernetes. Please contact your ITRS Account Manager to request this deployment.
Dedicated, hosted instance Copied
The instance runs in an AWS single-tenancy virtual private cloud (VPC). ITRS Cloud Operations run the platform.
Client cloud (BYOCloud) Copied
The instance runs in your organization’s single-tenancy VPC, and ITRS operates it. Confirm region, connectivity, and operational scope with your ITRS Account Manager.
BYOCloud is not the same as a Client-managed cluster (BYO cluster) deployment. In BYOCloud, ITRS operates the instance, while your team installs and operates ITRS Analytics in a BYO cluster.
Details such as region choice, two-availability-zone high availability, daily backups, and planned upgrades are in Deployment and resiliency planning.
Client-managed cluster Copied
Choose Client-managed cluster when your organization must self-host and Kubernetes is already part of your platform strategy. Your team installs ITRS Analytics on a Kubernetes cluster that your organization already operates (Bring-Your-Own cluster) and can use existing skills, tooling, and processes.
Supported hyperscaler platforms: Amazon EKS, Google GKE, and Azure AKS. Self-hosted Kubernetes is not recommended.
Note
Bring-Your-Own (BYO) cluster is not Client cloud (BYOCloud). BYOCloud is ITRS Managed. A BYO cluster is self-hosted.
Backup and restore is supported with Velero; your team schedules and runs it. For more information, see Backup and restore.
You can install ITRS Analytics on a Client-managed cluster with Helm charts (typically through GitOps) or with Kubernetes Off-the-Shelf (KOTS). Helm/GitOps is the primary production path, while KOTS is better suited for proof-of-value installs. Both paths support online and air-gapped clusters.
For Helm/GitOps, deploy the ITRS Analytics Helm charts through your organization’s GitOps process. Air-gapped installs are supported with Helm/GitOps.
For KOTS, choose the procedure that matches whether the cluster can reach the internet. Both procedures require a load balancer and an ingress controller.
- Install in an online Bring-Your-Own (BYO) cluster with KOTS — the cluster can pull images and download install files.
- Install in an air-gapped Bring-Your-Own (BYO) cluster with KOTS — no internet access. Your team needs a Docker registry, must mirror images, and should deploy and scan ITRS Docker images before install.
Before install, confirm Kubernetes clusters compatibility and resource and hardware requirements.
Application on VM Copied
Choose Application on VM when your organization must self-host and Kubernetes expertise is limited. Your team installs ITRS Analytics on virtual machines. The installer creates Embedded Cluster (k0s) on the hosts, so your organization does not need a Kubernetes cluster beforehand.
Note
Cluster issues must be escalated to ITRS because your team does not have direct access to the bundled K0s Kubernetes layer or its diagnostic tools. The environment is not elastic, so size the virtual machines properly before install. With enough spare capacity, a non-elastic cluster can still absorb a node failure and remain fully functional.
| Hosting arrangement | What it means |
|---|---|
| Instances on hyperscaler VMs | VMs in a public cloud (for example AWS, Azure, or Google Cloud). Your team installs onto the VMs, not onto EKS, GKE, or AKS. |
| Instances on self-hosted VMs | VMs your organization hosts, such as on-premises. |
Both arrangements use the same Embedded Cluster install procedures.
Choose the procedure that matches whether the hosts can reach the internet:
- Install in an online embedded cluster — the hosts can download the bundle and pull images. From ITRS Analytics 2.11.x, your team can add nodes; see Multi-node clusters with Embedded Cluster online.
- Install in an air-gapped embedded cluster — download the bundle on a connected machine and transfer it to the hosts. From ITRS Analytics 2.11.x, your team can add nodes; see Multi-node clusters with Embedded Cluster air-gapped. ARM64 is not supported.
Velero is not supported for the node-local storage this path uses. Arrange backups at the infrastructure level. See Backup and restore and Deployment and resiliency planning.
Before install, complete Set up your system for Embedded Cluster installation and resource and hardware requirements.
Note
For high availability, storage, and operational trade-offs, see Deployment and resiliency planning. For what backup is supported on each path, see Backup and restore. For sizing, see ITRS Analytics Sizer.