Skip to main content

Before you begin

Written by Aron Day

Who to talk to

If you are considering deploying 3B in a self-hosted environment, please first contact your Account Executive or Customer Success Manager to explore your options.

Following that conversation you’ll be put in touch with the right technical resources in Tines to help you access the 3B OCI registry, guide you through the installation, and provide ongoing support.

We highly recommend sharing the relevant pages in this section — particularly the system overview, connectivity requirements, and sizing — with your internal IT, infrastructure, network admin, and security teams early (as appropriate) to provision the infrastructure, services, and network connectivity required.

What you’ll need from Tines

Before installing, make sure you have:

  • OCI registry credentials — a tenant name (username) and API key for oci.tines.com. See accessing the OCI registry.

  • A release version — the version of 3B to install, for example 2.0.0. Tines will tell you the current version; releases are listed in the release notes.

  • A signed license token — a token beginning 3bl_v1_… that applies to the whole install. See applying a license.

Choosing a deployment model

3B self-hosted supports two deployment models:

Model

Best for

How it’s installed

Evaluations — proofs of value and proofs of concept

One command on a single Linux server. The installer sets up a lightweight Kubernetes (k3s) and deploys everything onto it.

Production, and anywhere you already run Kubernetes

The official Helm chart, installed onto your own cluster from oci.tines.com.

The single-server install has no high availability and no redundancy: if the server goes down, 3B goes down with it. Use it for evaluations, and use Kubernetes with the Helm chart for production.

Compatible environments

3B self-hosted artifacts are delivered as a Helm chart and a set of OCI container images, so 3B runs on a Kubernetes cluster whose nodes meet the requirements below. 3B has been deployed successfully in the following environments:

Kubernetes is the orchestration platform we recommend and support. Beyond the environments listed above, 3B will run on any conformant Kubernetes cluster once the requirements laid out in the system overview, connectivity requirements, and sizing pages are satisfied (though correct operation of the cluster and its underlying infrastructure remains the responsibility of the customer).

Next steps

  1. Review the reference architecture and share it with your infrastructure teams.

  2. Follow the deployment guide for your chosen model.

Did this answer your question?