kapp
aur
Our great sponsors
kapp | aur | |
---|---|---|
7 | 16 | |
859 | 1,640 | |
1.5% | - | |
8.1 | 8.0 | |
9 days ago | 18 days ago | |
Go | Haskell | |
Apache License 2.0 | GNU General Public License v3.0 only |
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.
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
aur
- How do you guys manage AUR compilation?
-
update/build aur -git packages
I haven't used aura in a while, but as far as I understand the command sudo aura -Au --devel will only update packages that need updates based on if there are new commits upstream. As of aura 3.0.0 the git clones are kept in /var/cache/aura/vcs and when aura checks if the package needs an update it just does a pull on the repo and checks if the version is newer, so you will only see packages listed that require an update. You can add the --force flag to rebuild all of them, but that will generally do a lot of unnecessary work rebuilding packages with no updates upstream.
- Dhall: A Gateway Drug to Haskell
-
My transition from Windows to Linux in an anti-customer age
Yes, you need to use the CLI to run that, but it's trivial to do so and a real package management system brings many advantages over exe installers. The AUR, inspired by BSD's Ports, is one of the major advantages of Arch. It's very rare to find a package that isn't supported.
[1] - https://aur.archlinux.org/packages/radarr
[2] - https://github.com/fosskers/aura
-
Yay not working?
Same here. Checked the github page and they're aware of it. Should be fixed soon. In the mean time I've been using aura. It's pretty great, should be more popular imo.
- Yay or Paru!!??
-
I was trying to make a cargo like tool for c++ but then I thought, "fuck c++"
That's why I use aura
-
7 Useful Tools Written in Haskell
I found the discussion of the reasoning interesting: https://github.com/fosskers/aura/discussions/657
-
Pamac, Manjaro's package manager GUI, has been blocked again from accessing the AUR due to it flooding the servers with requests
I've really enjoyed this one: https://github.com/fosskers/aura
- is yay safe/any good?
What are some alternatives?
kubevela - The Modern Application Platform.
paru - Feature packed AUR helper
argo-cd - Declarative Continuous Deployment for Kubernetes
yay - Yet another Yogurt - An AUR Helper written in Go
Flux - Successor: https://github.com/fluxcd/flux2
cardano-node - The core component that is used to participate in a Cardano decentralised blockchain.
kapp-controller - Continuous delivery and package management for Kubernetes.
xmonad - The core of xmonad, a small but functional ICCCM-compliant tiling window manager
ytt - YAML templating tool that works on YAML structure instead of text
linux-inotify - Haskell binding to inotify.
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.
linux-evdev - Deprecated in favor of the evdev package (https://hackage.haskell.org/package/evdev)