Skip to main content

Deploying Paybill on Kubernetes (AKS)

info

You should setup a PostgreSQL database manually to be used by Paybill. We recommend using Azure Database for PostgreSQL since this guide is for deploying using AKS.

Follow the steps below to deploy Paybill on a AKS Kubernetes cluster.

  1. Create an AKS cluster and connect to it to start with the deployment. You can follow the steps as mentioned on the Azure's documentation.

  2. Create k8s deployment

      curl -LO https://raw.githubusercontent.com/paybilldev/paybill/refs/heads/master/deploy/kubernetes/AKS/deployment.yaml

Make sure to edit the environment variables in the deployment.yaml. We advise to use secrets to setup sensitive information. You can check out the available options here.

info

For the setup, Paybill requires:

    • PB_DB
    • PB_DB_HOST
    • PB_DB_USER
    • PB_DB_PASS
    • PG_HOST
    • PG_DB
    • PG_USER
    • PG_PASS
    • APP_KEY

Read environment variables reference

info

If there are self signed HTTPS endpoints that Paybill needs to connect to, please make sure that NODE_EXTRA_CA_CERTS environment variable is set to the absolute path containing the certificates. You can make use of kubernetes secrets to mount the certificate file onto the containers.

  1. Create k8s service and reserve a static IP and expose it via a service load balancer as mentioned in the doc. You can refer service.yaml.

     curl -LO https://raw.githubusercontent.com/paybilldev/paybill/refs/heads/master/deploy/kubernetes/AKS/service.yaml

  2. Apply YAML configs

     kubectl apply -f deployment.yaml, service.yaml

You will be able to access your Paybill installation once the pods and services running.

Database​

Update Paybill deployment with the appropriate env variables here and apply the changes.

Upgrading to the Latest LTS Version​

New LTS versions are released every 3-5 months with an end-of-life of atleast 18 months. To check the latest LTS version, visit the Paybill Docker Hub page. The LTS tags follow a naming convention with the prefix LTS- followed by the version number, for example paybilldev/paybill:ee-lts-latest.

If this is a new installation of the application, you may start directly with the latest version. This guide is not required for new installations.

Prerequisites for Upgrading to the Latest LTS Version:​

  • It is crucial to perform a comprehensive backup of your database before starting the upgrade process to prevent data loss.

If you have any questions feel free to join our Discord Community or send us an email at info@paybill.dev.