install-zymtrace-backend

Install the zymtrace backend via Kubernetes Helm or Docker Compose.

5|1|Updated May 17, 2026
One-click install
npx skills add https://github.com/zystem-io/zymtrace-skills --skill install-zymtrace-backend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: install-zymtrace-backend
Source: https://github.com/zystem-io/zymtrace-skills/tree/main/zymtrace/skills/install-zymtrace-backend
Command: npx skills add https://github.com/zystem-io/zymtrace-skills --skill install-zymtrace-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines deploying the zymtrace backend so you can reliably ingest CPU/GPU profiling data and bring up the UI without manual, error-prone configuration.

Core Features & Use Cases

  • Kubernetes Helm backend installation: Guides setup for gateway, ingest, web/UI, symdb, identity, migrations, and required data stores.
  • Docker Compose backend install (single-node/PoC): Provides an alternative path for laptops and small demos without ingress/HA complexity.
  • Production-ready configuration decisions: Helps you choose license placement, database modes (create vs use existing vs managed Postgres variants), network exposure, auth type, and air-gapped registry settings.

Use case example: You want to deploy zymtrace on EKS with managed ClickHouse/Postgres/S3, configure TLS/ingress, and ensure secrets are created correctly so the backend becomes healthy.

Quick Start

Ask to install the backend by providing your cluster type and whether you use Helm on Kubernetes or Docker Compose, for example: "install zymtrace backend on my EKS cluster with external ClickHouse/Postgres/S3 and TLS enabled".

Frequently Asked Questions about install-zymtrace-backend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a backend on Kubernetes using Helm with managed Postgres and TLS?

To deploy a backend on Kubernetes with Helm and managed Postgres, you must configure storage/database mode selection, manage required secrets, and set up ingress TLS. Pre-flight checks and scripted verification ensure the Helm installation is production-ready.

What is the best way to configure database mode selection during a Helm backend deployment?

Database mode selection during Helm deployment involves choosing whether to create a new database, use an existing one, or connect to managed Postgres variants. This decision impacts how you template chart values and manage storage before executing the installation.

Can I install the zymtrace backend for a PoC without Kubernetes ingress complexity?

Yes, you can install the backend using Docker Compose for single-node evaluation or PoC environments. This path avoids Kubernetes ingress, high availability, and network/auth configuration complexity while still bringing up the UI and profiling data ingestion.

Does this Helm deployment support air-gapped Kubernetes environments?

Yes, the Helm deployment supports air-gapped installations by configuring air-gapped registry settings within the chart values. This allows you to pull images from a private registry without external network access during the backend installation.

How do I safely upgrade Helm chart values for a backend deployment without breaking configurations?

To safely upgrade Helm chart values, the installation enforces safe Helm upgrade semantics using reset-then-reuse-values and atomic installs. This prevents partial configuration updates and ensures the deployment rolls back if verification checks fail.

Do I need to manually configure Kubernetes network and auth settings before installing the backend?

You must address Kubernetes network and auth configuration as part of the backend installation process. The deployment guides you through configuring network exposure, auth type, and ingress TLS to ensure the backend services can communicate securely.