Search docs.molo17.com

    Deploy and operate Gluesync

    Start with the setup wizard at Get Gluesync. It provides the installation kit and standard setup flow. Use the manual deployment references only when your infrastructure team must control the container runtime itself.

    Choose a deployment path

    Path Use it when Guide

    Kit installer

    You want the supported default on Linux, Windows Server, or macOS. The Get Gluesync setup wizard prepares this path. The kit already includes Prometheus and Grafana.

    Install with the kit

    Docker Compose (DIY)

    Your operations team manages the container runtime and must inspect or customize every service.

    Deploy with Docker Compose manually

    Kubernetes and Helm

    Gluesync must run in an existing Kubernetes environment with your ingress, storage, and registry policies.

    Deploy on Kubernetes

    Offline

    The target environment cannot reach the Gluesync registry or other required Internet endpoints.

    Install and update offline

    Do not begin with the Docker or Podman references just because Gluesync uses containers. The setup wizard and kit handle the standard installation. Those pages are DIY references for system administrators who cannot use the default flow.

    Installation sequence

    1. Check system requirements.

    2. Request or download a Gluesync kit.

    3. Follow one deployment path from the table above.

    4. Sign in to the Control Plane.

    5. Build your first pipeline.

    Day-two operations

    Task Guide

    Prepare an evaluation for production

    Production readiness

    Update platform services

    Update Gluesync

    Update Gluesync on Kubernetes

    Gluesync Kubernetes Operator (GKO)

    Back up, restore, or duplicate configuration

    Backup and restore

    Perform routine administration

    Administration runbook

    Monitor pipelines and infrastructure

    Monitoring

    Configure alerts and notifications

    Alerting

    Diagnose a failure

    Troubleshooting

    Manual runtime references

    Use these only when the chosen deployment path requires you to manage the runtime yourself: