Kusion v0.9.0: A Dev-Centric DevOps Tool to Deliver Intentions to K8s and Clouds
medium.comIt looks neat, but at the same time, I don't get what is it trying to solve. Another declarative configuration language format (we already have YAML and HCL, now there is KCL) and I don't see how is it an improvement worth presenting this tool to my team. Secret management seems to be half assed: if Kusion was at least providing tools for integrating with solutions like Vault or Aws Secrets Manager then could alleviate huge pains, but right now it looks like it requires you to write additional glue and integrate it with Kusion somehow.
I don't want to invest my time into another declarative closed loop. Now that there is Pulumi it just doesn't make any sense to me. It allows to easily integrate all the parts of deployment process together using already known and more flexible tools than declarative languages could ever be.
Thank you very much for your feedback! Let me explain these questions.
1. Secret management: We did have a secret as code solution in a previous version, but we removed it because we upgraded our App model and the old user guide is not appropriate. We will refresh it later. The idea behind the guide is still the same. If you are interested in the older version, you can check out this link. (https://github.com/KusionStack/kusionstack.io/blob/b0fb8296d...)
2. Another declarative closed loop: Tools like Pulumi and Terraform mainly focus on provisioning resources but Kusion focuses on the software development life cycle(SDLC) which contains other components like rollouts, policies, monitoring, etc. In fact, Kusion is utilizing Terraform to manage cloud resources (https://kusionstack.io/docs/user_docs/concepts/kusion#runtim...). In other words, what Kusion wants is to build an open-source developer platform that can integrate your existing infrastructures to boost the App Dev's efficiency, not another wheel.
Kusion is an open-source project that is still in its early stages, and we are actively working on enriching our ecosystem. We are also looking for friends and partners to build this project together. Feel free to contact me and all feedback is welcomed and appreciated :)
Interesting idea and a cute mascot! Look pretty similar to the concept of terraform. From the example though I could see you are trying to encapsulate different cloud vendor’s product offerings (AWS RDS vs Azure CosmosDB for example) under the same abstract model (Database), which is a different philosophy from terraform. Wonder if that's gonna work.
Creating an abstract model that functions seamlessly across various cloud providers is undoubtedly challenging, and we are working on defining a guideline about how to abstract these resources with our project Kusion. We welcome any suggestions or ideas, so please feel free to reach out to us.