2,632 karma · joined June 19, 2019
- https://link-society.com
- https://krouter.cloud
- https://flowg.cloud
- https://linkdd.github.io
- https://david-delassus.medium.comThis makes me sad that this became an expectation. And yet, I've been distributing softwares via Docker for almost a decade now, but CLI/GUI tools?
And self-promotion a bit: https://github.com/link-society/flowg An easy to setup/use log processing facility:
Because OpenObserve didn't have the features I wanted
Because ELK is too heavy for my usecase
Because Splunk is too expensive
Because I wanted something KISShttps://github.com/SaaShup/netbox-docker-plugin & https://github.com/SaaShup/netbox-docker-agent
I am one of the contributors, and we use it extensively at work. There are still a few quirks to iron out, but it's a really nice experience.
Sure, you could make your own .deb, your own repository, and manage dependencies yourself. But do you really want to?
On-topic: Glasskube isn't really an ArgoCD plugin as it can work standalone, but in 2024, can you really propose a package manager for k8s without having some integration with ArgoCD and GitOps in general?
If you want to migrate, having interoperability between the tools can make the process smoother. And if you don't want to migrate and still benefit from a centralized, curated, audited repository of packages for Kubernetes so that your "Powered by ArgoCD" GitOps are easier to manage, that's what the GitOps template propose.
In Debian, you can just `apt install <that big thing i don't want to write a deploy script for>`. Imagine doing that with the usual big operators you want in your cluster (cert-manager, a hashicorp vault operator, istio or nginx ingress controller or envoy or ...)
The `glasskube install` command does a bunch of stuff that ends up as resources in your Kubernetes cluster, that are then interpreted by the Glasskube operator.
The "Gitops template" make use of ArgoCD and Git to do what `glasskube install` would have done.
I don't have any addon, I run a vanilla chrome+adblock.
Is suspected the DNS as well, but `nslookup` is instantaneous most of the time.
IMHO, many Helm charts could be replaced by a simple Kubernetes operator, and the MetaController would be a great asset for that.
I like to output structured log anyway. Not JSON as it's not really human readable but at least in "logfmt" format[1] as it's both human readable and easy to parse.
FYI, Go provides `log/slog` which offers structured logging in both formats (JSON and logfmt).
Rust binaries are static, which means they need to be rebuilt when security fixes are published on one of their dependencies.
Without active development to at least update, the static binary becomes a liability.
On another note, the developers on exa did explicitly say the project was unmaintained:
https://github.com/ogham/exa/commit/fb05c421ae98e076989eb6e8...
Since when you give up shared libraries, you give up on security upgrades without needing to rebuild the world.
Here is the "friend link" bypassing the paywall: https://david-delassus.medium.com/unity-like-coroutines-in-p...
I've known C for almost 20 years, and never would I have thought the macro system was powerful enough to allow such black magic.
This is awesome!
What if Ray the person was named after ray-tracing by his parents?
For scanning, I use OpenFoodFacts, it's a collaborative/opensource project: https://github.com/openfoodfacts