---
title: Operational Flow
slug: operational-flow
description: Learn how the Kubeark platform uses a hierarchical structure, with clusters as the top level, to manage containerized applications. Discover how template groups and their multiple versions simplify configuration file management. Explore deployments and th
docTags:
createdAt: 2023-07-19T12:45:55.996Z
---
The Kubeark platform operates on a hierarchical structure, where each level builds upon the previous one. This structure is as follows:
1. **Clusters****:** This is the highest level in the hierarchy. The Kubeark platform requires the use of a Kubernetes cluster as the fundamental unit of organisation. The Kubernetes `cluster` is a collection of physical or virtual machines that are connected and operate together to run containerized applications.
2. **Template Groups**: Groups serve as containers for all the templates that you create. You can have multiple `Groups`, each with its own set of templates.
3. **Templates**: Templates are the next level in the hierarchy. They are essentially configuration files that define the resources needed for a given deployment. Each Product can have multiple templates, but the number of templates you can create is limited by your license.
4. **Versions**: Each template can have an unlimited number of versions. The versioning system allows you to track changes made to templates over time, and revert to previous versions if necessary. Only one version of a template can be active at a time, meaning that only the active version can be deployed.
5. **Deployments**: Finally, the `Deployments` level is where you deploy your templates. Each template that is configured and ready for production becomes an Deployment. You can update the deployment of previous versions to the active version to ensure they are running the latest configuration.
