Deploying Chronicle on Sawtooth¶
Chronicle on Sawtooth cannot be deployed unless you have access
to BTP's official docker image registry. Once you have acquired the credentials
for this registry from BTP you will need to create the target namespace for your
deployment and create an image pull secret in that namespace that you can
reference later. In this example the
chronicle-namespace and the image pull secret is
Chronicle on Sawtooth in the deployments marketplace takes you to
its deployment form. Here you need to give your deployment a name
and specify its namespace using the one created above:
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.
Chronicle on Sawtooth deployment is running it is possible to expose
various Sawtooth features using Kubernetes services. This is covered in depth
Beyond configuring Sawtooth itself these are the deployment options supported by Sextant.
This option allows you to specify, for example, a custom transaction processor.
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.
This option allows you to change the genesis seed on redeployment.
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.