Ingest, store, & analyze all types of time series data in a fully-managed, purpose-built database. Keep data forever with low-cost storage and superior data compression. Learn more →
Kapp Alternatives
Similar projects and alternatives to kapp
-
-
-
InfluxDB
Access the most powerful time series database as a service. Ingest, store, & analyze all types of time series data in a fully-managed, purpose-built database. Keep data forever with low-cost storage and superior data compression.
-
-
-
-
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.
-
homebrew
Provides tools from https://carvel.dev via Homebrew package. (by carvel-dev)
-
SonarQube
Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
-
terraform-provider
Carvel Terraform provider with resources for ytt and kapp to template and deploy to Kubernetes
-
-
-
-
Hasura
Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
-
-
-
hledger
Robust, fast, intuitive plain text accounting tool with CLI, TUI and web interfaces.
-
lens
Lenses, Folds, and Traversals - Join us on web.libera.chat #haskell-lens (by ekmett)
-
-
taskell
Command-line Kanban board/task manager with support for Trello boards and GitHub projects
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better kapp alternative or higher similarity.
kapp reviews and mentions
Posts with mentions or reviews of kapp.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-28.
- 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:
-
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:
-
A note from our sponsor - InfluxDB
www.influxdata.com | 27 Mar 2023
Stats
Basic kapp repo stats
7
734
8.1
4 days ago
carvel-dev/kapp is an open source project licensed under Apache License 2.0 which is an OSI approved license.
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com