Overview

In this article, we will provide an overview of the core concepts of Kusion from the perspective of the Kusion workflow.

The workflow of Kusion is illustrated in the diagram above, which consists of three steps.

The first step is Write, where the platform engineers build the Kusion Modules and initialize a Workspace. And the application developers declare their operational intent in AppConfiguration under a specific Project and Stack path.

The second step is the Build process, which results in the creation of the SSoT (Single Source of Truth), also known as the Spec of the current operational task. If you need version management of the SSoT, we recommend you manage the Spec with a VCS (Version Control System) tool like Git.

The third step is Apply, which makes the Spec effective. Kusion parses the operational intent based on the Spec produced in the previous step. Before applying the Spec, Kusion will execute the Preview command (you can also execute this command manually) which will use a three-way diff algorithm to preview changes and prompt users to make sure all changes meet their expectations. And the Apply command will then actualize the operation intent onto various infrastructure platforms, currently supporting Kubernetes, Terraform, and On-Prem infrastructures. A Release file will be created in the Storage Backend to record an operation. The Destroy command will delete the resources recorded in the Release file of a project in a specific workspace.

A more detailed demonstration of the Kusion engine can be seen below.