Deployment

Kuvasz can be easily deployed to any container based environment, since its only dependency is a PostgreSQL database. You don't have to worry about database schema migrations between version updates, because the application takes care of them before it actually starts.

By design, most of Kuvasz's features can be configured through environment variables, you can find a reference of them here.

Before you deploy Kuvasz, you should also take a look at the Distributions section to have a better understanding of the JDK vs. native image topic.

Resource limits

If you want to set up a resource limit for Kuvasz in your environment, you should be aware of that the service needs at least 384 MiB of memory to remain stable.

A minimal setup for your resources would look like this in Kubernetes:

# ...
resources:
  requests:
    memory: 154Mi # Pay attention to this limit!
    cpu: 1024m
  limits:
    memory: 384Mi # Pay attention to this limit as well! It's the lowest memory limit you can set to have a stable service
    cpu: 1024m
# ...

Health checks

Kuvasz provides a /health endpoint for readiness probes out of the box.

Further examples

You can find more concrete examples here:

• Kubernetes
• docker-compose