Preview Environment
On Ownkube, related deployments are organized into environments: named groupings like Development, Staging, or Production, each with its own configuration but sharing the same underlying cluster. A preview or staging environment is a common pattern for testing changes before they reach production, without needing a separate cluster.
Every organization starts with two default environments, Development and Production, and you can create as many more as you need, such as a staging or qa environment for pre-release testing. Each environment is scoped to a cluster, and deployments within it share a logical boundary: each deployment keeps its own environment variables, replica scale, and image tag per environment, and the same deployment name can exist in both Development and Staging on the same cluster, since uniqueness is scoped to the cluster-and-environment pair. Color-coded badges make it visually obvious in the dashboard which environment you’re looking at.
A preview or staging environment lets you validate a change against production-like conditions before promoting it, without provisioning separate infrastructure. On Ownkube-managed compute, environments run side by side with nothing to provision; on an own-cloud cluster, you can also split environments across clusters entirely, for example a cheap Starter cluster for development and a highly available Production cluster for live traffic.