ketch VS cnab-spec

Here at Suse we looked at https://github.com/theketchio/ketch and the founder for Acorn did some diligence there. Is it a copy?

An idea may be to look at something like Ketch, and potentially combine it with Pulumi, TF, or others. Here is an example

You have some more “established” tools, such as Ketch but from what I’ve seen, many people are building it in house by using tools such as Helm, Crossplane, or others

Pretty much what Ketch has been doing for a while already, and Ketch is part of a larger app platform

Pretty much what Ketch has been doing for a while now

Another option you have is to use open source projects like Ketch that can make this process more "developer friendly". Here is an example

Because of that, we have created an open-source project called Ketch to make life easier when deploying apps on K8s.

The team is excited about enabling developers to focus on their application code instead of infrastructure. We would love it if you could show your support by starring the project on GitHub and sharing this article with your teammates.

It might be worth having a look at the open source project Ketch

Instead, by combining the application-focused approach from Ketch with the IaC model from Pulumi, developers can have an application-focused layer they can leverage to quickly deploy their applications without getting into the underlying infrastructure details exposed by Kubernetes.

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.