kubevela
kapp
Our great sponsors
kubevela | kapp | |
---|---|---|
27 | 7 | |
6,062 | 859 | |
2.4% | 1.5% | |
9.0 | 8.1 | |
6 days ago | 10 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kubevela
- Is there any Django app deployment tool for VPS-based environments with UI?
- What's the status of Open Application Model?
-
Using compose files as a universal infrastructure interface, even for Kubernetes
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.
- Helm or Kustomize for my situation?
- KubeVela, the extensible engine for IDP and platform engineering
-
Opinionated application platform on top of Kubernetes?
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
-
Finding better motivations for software work (Other than pride)
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
- Kubevela - The modern application platform.
-
Clusterpedia —— Cluster API Searching Has Never Been Easier
Also, kubevela is getting ready to connect to clusterpedia https://github.com/kubevela/kubevela/issues/4237,
-
Acorn
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.
kapp
- HELM vs KUSTOMIZE
-
How to handle the lifecycle of multiple COTS
If you want to take it one step further: you might be applying several resources at a time that are logically one "application". kapp (https://carvel.dev/kapp/) lets you group those together and give them a name, and provides a "terraform-like" experience where it shows you its execution plan before applying updates. So then you might do `ytt -f | kapp deploy -a name-of-thing` Or you could use helm's templating engine but then still pass the resulting yaml to kapp for its unification of the deployment step.
-
Dhall: A Gateway Drug to Haskell
since you mentioned Kubernetes...
> It would be nice if there was a separate state reconciliation system that one could adapt to use with Cue or Dhall or any other frontend
this exactly was thinking behind https://carvel.dev/kapp for Kubernetes (i'm one of the maintainers). it makes a point to not know how you decided to generate your Kubernetes config -- just takes it as input.
> In particular the ability to import other files as semantic hashes seems like a great feature.
it's an interesting feature but seems like it should be unnecessary given that config can be easily checked into git (your own and its dependencies).
-
Terraform should have remained stateless
i think kubernetes is not a great example in favor of more client state (like tf) since k8s has uniform resource structure (metadata.*) and first class labeling support. but as you point out kubectl doesnt use labels well (at least imho).
when building https://carvel.dev/kapp (which i think of as "optimized terraform" for k8s) the goal was absolutely to take advantage of those k8s features. we ended up providing two capabilities: direct label (more advanced) and "app name" (more user friendly). from impl standpoint, difference is how much state is maintained.
"kapp deploy -a label:x=y -f ..." allows user to specify label that is applied to all deployed resources and is also used for querying k8s to determine whats out there under given label. invocation is completely stateless since burden of keeping/providing state (in this case the label x=y) is shifted to the user. downside of course is that all apis within k8s need to be iterated over. (side note, fun features like "kapp delete -a label:!x" are free thanks to k8s querying).
"kapp deploy -a my-app -f ..." gives user ability to associate name with uniquely auto-generated label. this case is more stateful than previous but again only label needs to be saved (we use ConfigMap to store that label). if this state is lost, one has to only recover generated label.
imho k8s api structure enables focused tools like kapp to be much much simpler than more generic tool like terraform. as much as i'd like for terraform to keep less state, i totally appreciate its needs to support lowest common denominator feature set.
common discussion topics:
-
Is there any CLI tool to sync between local yamls and current cluster namespace state?
Take a look at kapp (https://github.com/vmware-tanzu/carvel-kapp).
-
Deploy Neo4J's APOC plugin with code thanks to CARVEL vendir
kapp - Install, upgrade, and delete multiple Kubernetes resources as one "application"
-
Open Application Model – An open standard for defining cloud native apps
I really like this approach for simplifying Kubernetes. A few projects similar to OAM in that it provides a higher level "Application" CRD:
https://github.com/vmware-tanzu/carvel-kapp
What are some alternatives?
crossplane - The Cloud Native Control Plane
argo-cd - Declarative Continuous Deployment for Kubernetes
Flux - Successor: https://github.com/fluxcd/flux2
kustomize - Customization of kubernetes YAML configurations
kapp-controller - Continuous delivery and package management for Kubernetes.
rancher - Complete container management platform
ytt - YAML templating tool that works on YAML structure instead of text
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
carvel - Carvel provides a set of reliable, single-purpose, composable tools that aid in your application building, configuration, and deployment to Kubernetes. This repo contains information regarding the Carvel open-source community.
porter - Kubernetes powered PaaS that runs in your own cloud.
terraform-provider-carvel - Carvel Terraform provider with resources for ytt and kapp to template and deploy to Kubernetes