Maintenance
Last updated: June 10, 2026
| Tier | Deployment |
|
|
Maintaining a robust, stable, and scalable deployment of Sisense on Linux (or in Kubernetes) requires more than just an initial installation. Over time, as data volume grows, usage patterns change, and infrastructure evolves, administrators must perform maintenance tasks to expand capacity, ensure availability, migrate environments, and keep services healthy. The following topics comprise a set of core operational, maintenance-related, areas that every Sisense operator should understand and plan for:
-
Expanding Storage Capacity (Persistent Volumes) — how to grow storage allocations when data volumes (e.g. ElastiCubes, logs) outgrow initial provisioning.
-
Scaling Up: From Single-Node to Multi-Node Deployments — how to transition an existing single-node deployment into a multi-node (clustered) deployment while preserving existing assets, enabling higher availability, performance, and scalability.
-
Running Multiple Instances of Sisense — how to operate more than one Sisense deployment (e.g., separate environments for staging, production, testing, or multiple customers) on shared or distinct infrastructure.
-
Maintaining Kubernetes Certificates — ensuring that TLS / Kubernetes-level certificates (used for internal services or K8s control-plane, if relevant) remain valid; renewing them when expiry approaches to avoid service disruption.
-
Migrating Sisense Between Environments — how to safely migrate from one environment to another (e.g., dev > production, or one server/cluster to another), including considerations for backing up and restoring assets.
-
Managing Services and Using the Sisense CLI — how to use the built-in command line tools (and review currently running services) to perform maintenance operations, health checks, backup & restore, and other operational tasks.
Together, these maintenance topics define the ongoing lifecycle responsibilities of running Sisense in production: ensuring you have enough storage and compute capacity, enabling growth, supporting multiple environments, preserving uptime, migrating cleanly, and maintaining infrastructure hygiene.