In this section, we will introduce the architecture of KusionStack and some core concepts.
KusionStack includes two core components:
This page lists and defines technical terms that are widely used across KusionStack. Words such as Project, Stack, etc. can be overloaded in the technical community, so this page attempts to clarify their meaning in the context of KusionStack.
📄️ How Kusion Works
Kusion is the platform engineering engine of KusionStack. It delivers intentions described with Kusion Models defined in Catalog to Kubernetes, Clouds and On-Prem infrastructures.
The Intent represents the operational intentions that you aim to deliver using Kusion. These intentions are expected to contain all components throughout the software development lifecycle (SDLC), including resources (workload, database, load balancer, etc.), dependencies, and policies. The Kusion module generators are responsible for converting all AppConfigurations and environment configurations into the Intent. Once the Intent is generated, the Kusion Engine takes charge of updating the actual infrastructures to match the Intent.