kubevela VS cnab-spec

Finally, I think the OAM model offers one possible future. Take a look at projects like KubeVela and Crossplane. These allow you to compose your own custom abstraction layer. The developer creates a simple CRD called "Application" and this is translated into ths k8s or even off-cluster resources. Problem right now is the complexity is transferred onto guys configuring the platform..... I want to see more "out of the box" implementations.

Gotcha, thanks! We already run ArgoCD but having devs write raw manifests feels so low-level when it’s usually the same combo of configmaps, ingresses, services, deployments… Maybe this is more in the direction of what I’m looking for? 🤔 https://kubevela.io

Note: On that topic, I'm keeping a close eye on the Open Application Model and the kubevela projects. I think it’ll help write a representation of an application and its components that we can validate the structure of our code against, and generate documentation from it. Not a complete solution to the problem, but it'll help with certain parts of architecture documentation

Also, kubevela is getting ready to connect to clusterpedia https://github.com/kubevela/kubevela/issues/4237,

https://kubevela.io/ is an alternative that has been around longer, exposes CUE naturally, and builds on open standards for app packs. I'd recommend this open-source product.

CNAB

Similar to https://cnab.io/ then?

IMO Cloud native application bundle is what you are looking for: https://cnab.io/

have you looked at CNAB ? since it uses standard OCI compliance you can have your entire application bundle on Azure registry (azure registry is OCI 2 compliant registry) and you can get more information about how to do it using ORAS cli

Check https://cnab.io/ and https://porter.sh/

I'm closely tracking an effort by Microsoft that aims to do a lot of what you're describing since I find myself bridging between these tools and deploying stacks that span tools and roles. [CNAB](https://cnab.io/) and the front-running implementation, [Porter](https://porter.sh/), enable one-step infra deployments, packaged as a single OCI-compatible container, with any number of steps, using the best tools for each of those steps. Think of using aws-cli for some initialization step (create or verify presence of a state bucket), applying some terraform to create infra, and finishing with a helm chart to complete deployment of app components. Each stage in a bundle packages not only the code to run it but also the execution binary of the tool that runs it. The spec and porter are still a moving target but it's a promising space and a nice adjacent evolution of the current state of tooling.