Installations & Environments

Installations & Environments

An installation refers to a Kadeck instance or multiple Kadeck instances that share a database (e.g., PostgreSQL)  and run in a cluster configuration (with upstream load balancer).

Multiple Apache Kafka clusters

One Kadeck installation can manage multiple Apache Kafka clusters in parallel. This means that there is no need for a single environment per Apache Kafka cluster, but multiple Apache Kafka clusters can be managed by a single Kadeck environment.

Splitting environments

However, we advise our customers to have at least two different environments that are on separate networks:
  1. Production
  2. Non-Production
Non-Production can be further split into more environments as needed (e.g., UAT and DEV or based on departments).

There are, at least, a few reasons to separate Production from Non-Production in our opinion:
  1. It reduces attack surfaces as the production environment can be network isolated from the non-production environment.
  2. Stricter access controls can be implemented in the production environment across all resources.
  3. Reduces the risk of mistakes and hard to recover errors in production.
  4. Allows for faster experimentation in non-production as the cluster can be quickly reset completely.
Kadeck licenses do not work across installations. Any user that needs to access multiple installations will occupy a license per installation.