Bahriya Tersane

Installing a chart

Before you begin

  • Helm 3 on the machine that installs releases, with the Tersane repository added as described in Access and credentials.
  • kubectl access to the target cluster and namespace.
  • The image pull secret in the target namespace, if the chart runs images from 1x.ax.
  • A cluster built with the Bahriya Kubernetes Engine, or a cluster that provides what the charts expect, as set out in Running Tersane without BKE.

Keep your values in a file

Every chart ships with the values that run bahriya.cloud. Write the values that differ for your installation in a file you keep under version control, and pass that file on every installation and every upgrade. The file is then the complete record of how the release differs from the chart’s defaults, and an upgrade never depends on values typed once at a terminal.

Each chart’s page lists its values. A minimal file for a standalone MySQL instance:

mode: standard
mysql:
  database: orders
imagePullSecrets:
  - name: 1x-ax

Install

helm install orders-db tersane/mysql \
  --namespace data --create-namespace \
  --version <chart version> \
  -f orders-db.values.yaml

Name the chart version explicitly, so that two installations made from the same command and file are the same release.

Confirm the release

helm status orders-db --namespace data
kubectl get pods --namespace data

A pod that stays in ImagePullBackOff usually means the pull secret is missing from the namespace or is not named in imagePullSecrets. A pod that stays in Pending usually means the cluster cannot provide the storage class the chart asks for; see Running Tersane without BKE.

Some decisions are taken once, at installation, and cannot be changed by a later upgrade. They are listed in Upgrading a chart; read that page before installing anything that will hold data.