This message was deleted.
# general
s
This message was deleted.
h
Interesting so basically argocd + crossplane with abstration on top?, the blog post is a bit confusing without comparisons
k
Good idea - so it's in the end an API layer that accepts a declarative application model as input and then dynamically create the representation of the application at deployment time. The orchestrator can be fed with crossplane, TF, really any IaC and it can hand over to Argo as well. What it comes down to is a new approach to configuration management. Dynamic configuration management.
To quote this:
approach to configuration management whereby an entire application, including its dependent infrastructure resources, is described in a Declarative Application Model. This model is consistent across any environment. The deployable representation is generated with every deployment and results into the running application. Applications configured using this dynamic approach are easier to maintain, easier to operate for developers, and allow for higher standardization.
h
Ahh makes more sense now, I read some of the other blog posts about it, how is it different from https://oam.dev/ , think people might draw comparisons to it ☺️
k
Good one! OAM is K8s based. This model doesn't care about what resources + runtime environments it orchestrates.