awesome-k8s-tools
kapp
Our great sponsors
awesome-k8s-tools | kapp | |
---|---|---|
5 | 7 | |
632 | 859 | |
- | 1.5% | |
9.7 | 8.1 | |
4 days ago | 10 days ago | |
Shell | Go | |
MIT License | 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.
awesome-k8s-tools
-
Ask r/kubernetes: What are you working on this week?
https://github.com/vilaca/awesome-k8s-tools is a project I've started about 9 months ago. This project aims to rank a comprehensive list of Kubernetes/container related OSS projects, sorted by stars. Every early morning, a GitHub action retrieves repositories from https://github.com/vilaca/awesome-k8s-tools/blob/main/data/repos and updates the README file accordingly. Initially, I intended for it to be another "awesome_X" list, but later I realised that there were already a few similar lists for Kubernetes, and the format didn't quite fit. Nonetheless, I've diligently maintained and updated the project almost every week, ensuring it remains a valuable resource. I often rely on it personally, and I believe it can be helpful to others in search of Kubernetes tooling. To further enhance the project, I am currently exploring new features. One idea is to generate a GitHub page (instead), providing a more user-friendly interface for browsing the list. This page could include additional details about each tool, such as concise descriptions, documentation links, and even user ratings or reviews. I would also like to encourage contributions from the community. If you know of any repositories that should or shouldn't be included in the list, I warmly welcome pull requests. You can find guidelines for contributing in the project's README, which will help maintain the list's relevancy and accuracy over time.
-
I've been collecting a list of k8s/container tools and sorting them by the number of stars in Github, so far the most complete k8s/container list I know of with almost 250 entries - hoping this is useful for someone else besides me - looking for feedback, ideas for improvement and contributors
Here's the file that acts as a database https://github.com/vilaca/awesome-k8s-tools/tree/main/data and here's the scripts that generates the README https://github.com/vilaca/awesome-k8s-tools/tree/main/build
-
Helm release time-to-live(TTL) to schedule automatic release uninstallation
This is really cool. I expect to test it this week on some pipelines. I also added to a list of k8s/container tools I maintain on https://github.com/vilaca/awesome-k8s-tools/
-
Using GitHub for knowledge documentation and sharing
I'm doing something in the same spirit here: https://github.com/vilaca/awesome-k8s-tools
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