Deploying Daml on Postgres¶
IMPORTANT If you intend to use AWS Aurora then you will need to prepare your target EKS Cluster by following the instructions here.
Note that you only have to do this once and if you have already deployed Daml on QLDB using your target cluster then this step will already have been completed.
Daml on Postgres in the deployments marketplace takes you to
its deployment form. Here you need to give your deployment a name, specify its
namespace and decide whether you want Sextant to create a Postgres database
Local option) or use a Postgres instance supplied by you (the
In this example we've opted for the local option and to enable persistence and
gp2 as the storage class as we are using AWS:
Then you need to scroll down and supply your Postgres credentials. Here we've opted
to supply a password but you can also provide a secret containing the field
password and your preferred password:
Deploy and the deployment will be created and added to the cluster:
Note that this deployment includes a
Settings option - the gear icon - which
is covered here.
Once your deployment has been added, you can view and interact with it as described here.
Deployment is not instantaneous as under the covers Sextant uses the appropriate helm chart to create your deployment which may involve pulling the appropriate images if these aren't already cached by the Kubernetes cluster.
In the case of a
Daml on Postgres deployment it may also include the creation
of a Postgres database.
Daml on Postgres deployment is running it is possible to expose various
Daml features using Kubernetes services. This is covered in depth
Beyond specifying whether you want to enable persistence for your deployment these are the options supported by Sextant:
Image Pull Secrets¶
This option allows you to specify any image pull secrets that may be required in order to access images related to your deployment that are hosted in a private repository. These all need to be available in your target namespace.
Advanced Deployment Customization¶
This option provides advanced users with the ability to specify Additional YAML which will override default template options. We recommend that you discuss any proposed customization with us first.