High Availability

Deploy Bindplane Server to Kubernetes with High Availability

Architecture

When Bindplane is deployed as a Deployment, it has the following architecture.

  • Bindplane with multiple replicas

    • Deployed as a Deployment.

  • Prometheus time series database

  • One or more Transform agent pods, for live preview

  • PostgreSQL storage backend

NOTE

Bindplane uses Prometheus as a storage backend for collector throughput metrics. It is unnecessary to manage Prometheus outside of the Helm chart.

NOTE

PostgreSQL is not deployed by the Bindplane Helm chart and must be deployed as a prerequisite.

Prerequisites

Licensing

An Enterprise license is required when operating Bindplane in High Availability. Learn more here.

PostgreSQL

PostgreSQL must be deployed and reachable from the cluster.

Postgres requirements

  • Database named bindplane

  • User with full permission to the bindplane database

  • Reachable from Bindplane's Kubernetes cluster

Event Bus

Bindplane requires an external event bus when operating with more than one pod. See the Event Bus documentation for details.

Installation

Add the Bindplane Helm chart to your workstation.

Create a values.yaml file, which will be used to configure your Helm deployment.

  • license: Your Enterprise license. Add the initial options. Make sure to set the following:

  • config.username: Your basic auth username for the Administrator project.

  • config.password: Your basic auth password for the Administrator project.

  • config.sessions_secret: A random uuid. You can use uuidgen to create one.

  • config.eventbus.type: The event bus type to use. This example will use Google Pub/Sub.

  • backend.postgres.host: The Hostname or IP address of the PostgreSQL server.

  • backend.postgres.port: The PostgreSQL server's port.

  • backend.postgres.username: The username the Bindplane server should use to connect to Postgres.

  • backend.postgres.password: The password the Bindplane server should use to connect to Postgres.

Deploy Bindplane to the bindplane namespace using Helm and your previously created values.yaml configuration file.

After a few moments, check the namespace by running kubectl -n bindplane get pod. You will see three pods.

Last updated

Was this helpful?