Skip to content

v0.10.0
Compare
Choose a tag to compare
@healthjyk healthjyk released this 15 Jan 10:04
· 228 commits to main since this release
v0.10.0
f7c8fed
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Features

Collaboration Paradigm

Introduce the collaboration paradigm between application developers and platform engineers. Due to the mixed configuration and unclear division of labor, the application developers have to face the high cognitive burden, while the platform engineers have great difficulty in standardization management. Hence, we make the huge upgrade —— proposing the collaboration paradigm between application developers and platform engineers and the core workflow, implementing the separation of concerns, to improve the efficiency and standardization.

The platform engineers are responsible for creating Kusion modules and maintaining workspaces. A module is a reusable building block, and contains two components: an application developer-oriented schema and a module generator. By the application developer-oriented schema, platform engineers shield the underlying complexity and achieve standardization.

The application developers are responsible to write AppConfiguration, which are composed of the developer-oriented and dead-simple schemas. There are few or even no complex configs for application developers, which reduce the cognitive burden of them.

For more detail, please refer to How Kusion Works?

Workspace Management

Introduce workspace and integrate it into the Kusion core workflow. The workspace is a logical concept representing a target that a stack will be deployed to, which contains a set of configurations that can be reused by multiple stacks. We recommend workspaces grouped by SDLC phases (such as dev, staging, and prod) or cloud vendors (such as AWS, Azure, and Alibaba Cloud).

The workspace contains four types of configurations: modules, runtimes, backends and secretStore, while the configuration is organized in YAML. We provide command lines to get, show, create, update, and delete workspace.

For more detail, please refer to Workspace.

Secret Management

Upgrade secret management in the new collaboration paradigm, and support more providers. Define the new core workflow of secret management in the collaboration scenario. Support storing sensitive data in Vault, AWS, Azure and Alibaba Cloud.

For more detail, please refer to Secrets and Using Cloud Secrets Manager.

AppConfiguration Revamp

Revamp the AppConfiguration according to the collaboration paradigm. Stripping platform configuration, the AppConfiguration only contains application developer-oriented configs. Splitting Database schema into MySQL and PostgreSQL, for better user experience.

For more detail, please refer to AppConfiguration.

Bug Fixes

  • Fix the recurring prompt ProjectName when using kusion init.
  • Fix NPE bug when using kusion apply --watch.

Deprecations

  • No longer support kusion compile, use kusion buildto replace it.
  • Deprecate core concept Spec, use Intent to replace it.
  • The state file is stored in the kusion_state.yaml, not kusion_state.json.

Docker Images

  • kusionstack/kusion:v0.10.0
Assets 6
Loading