Skip to content

Deployment Process

Deploying a punch first requires to deploy a kast instance with the required components. Refer to the kast documentation to understand the kast deployment logic and process.


Deploying kast is very similar to deploying a VM punch. You first define a few configuration files, and the kast deployer takes care of deploying everything to the target servers. If you are used to the punch deployer, you will be at ease with the kast deployer.

The precise process is as follows:

  1. Select the components required by your punch application. For example : kafka, minio, clickhouse and grafana.
  2. Define and setup your hosting server infrastructure. This typically consists in creating the required VMs (or native servers) with the required CPU, RAM and disk resources, making sure the networking, NTP and DNS are properly setup.
  3. Deploy these component using the kast deployer. Refer to the Kast Getting Started Guide for a quick overview.
  4. Deploy the punch console. The punch console provides you with the ops command to manage the punch applications.
  5. Deploy the punch adds on. These are provided as container images and helm charts.
  6. Move on to the operation setup to setup some runtime configurations items required before you can actually run the applications. This typically consists in creating a namespace, provisionning some resources such as database tables or S3 buckets, etc..