Installation options
- Option 1: Self-Hosted Standard Edition
- Option 2: Self-Hosted Custom Edition (Kubernetes or Red Hat OpenShift Container Platform)
- Option 3: Self-Hosted Classic Edition (Docker)
To install and configure the self-hosted Instana backend, you have 3 installation options: a single-node or multi-node cluster setup, Kubernetes cluster setup, and single- or dual-host Docker setup.
Option 1: Self-Hosted Standard Edition
Instana is deployed on a single-node or multi-node cluster, which needs lesser memory and infrastructure as compared to a Kubernetes cluster.
For more information, see Installing a Self-Hosted Standard Edition.
Option 2: Self-Hosted Custom Edition (Kubernetes or Red Hat OpenShift Container Platform)
The Custom Edition is the most scalable and flexible option, where Instana is deployed on a Kubernetes cluster, providing a highly available and fault-tolerant infrastructure.
The benefits of Custom Edition include high scalability and flexibility, strong high-availability options, and ease of deployment and management. However, deploying a Kubernetes cluster requires more investment in infrastructure and Kubernetes management expertise.
For more information, see Installing Self-Hosted Custom Edition (Kubernetes or Red Hat OpenShift Container Platform).
Option 3: Self-Hosted Classic Edition (Docker)
The single-host installation is a lightweight, easy-to-use option that is ideal for small- to medium-sized environments. It involves running Instana on a single host with all the necessary components of the Instana platform as Docker containers.
The benefits of this installation method include its simplicity and quick setup, low resource requirements, and suitability for testing and development. However, this installation method has limited scalability, lacks redundancy, and offers limited high availability options.
For information about how to install Self-Hosted Classic Edition (Docker), see Installing Self-Hosted Classic Edition (Docker).
The dual-host installation is designed for environments where ClickHouse is deployed on one host with a ZooKeeper installation. The rest of the Instana components and data stores are deployed on a second host.
This approach allows for better scalability of ClickHouse separately from the rest of Instana, based on requests per second (load). Resource allocation can be more efficient with separate hosts as more resources can be allocated independently to Instana and ClickHouse as they require more CPU or memory.
However, a dual-host setup is slightly more complex than a single-host setup, as two hosts need to be maintained and configured, requiring more infrastructure.
For information about how to create a Dual-host Instana setup on Docker, see Installation: Dual-host.