Backpack Battles! Fantastic little inventory management game with a load of replay value.
OP, my personal preference is to supply raw k8s manifests in a project. These are far easier to manipulate using tool called kustomize. Just think of it as an alternative to helm. The big thing is that kustomize removes the need for forks because it can run against manifests defined by a url.
It looks safe to me in the sense that I don’t see any malicious code in here. I don’t think the committee is trying to sneak in security hopes or similar. So all good on from that perspective.
It’s a very simple helm chart which is consideration! Here’s the thing with charts. They’re meant to be an official means of distributing your app’s manifests for k8s. One package with all runtime needs defined. If the chart supports every tweak I need, then it’s great! If it doesn’t, then I need to modify it myself. This usually means forking the project, making edits, and templating from the fork. It’s a lot of overhead for end users. If the maintainer is willing, it’s so much easier to create an issue or submit a PR with the needed changes.
Your project has some stars and forks. People are likely using it. Grats! The helm chart doesn’t like meet everyone’s needs and I would expect this to spur some extra issues and PRs. Is that good or bad? That’s up to you!!
There are many reasons to use k8s. Managing multiple nodes is one good one. But more importantly, k8s gives you an api-driven runtime environment. It’s really not comparable to docker compose.
Yea I’m not a fan of helm either. In fact, I avoid charts when possible. But kustomize is great.
I feel the same way about docker compose. If it wasn’t already obvious, I’m biased in favor of k8s. I like and prefer that interface. But that’s just preference. If you like docker compose, great!
There’s one point where I do disagree however. There are scenarios where a local k8s cluster has a good and clear purpose. If your production environment runs on k8s, then it’s best to mirror that locally as much as possible. In fact, there are many apps that even require a k8s api to run. Plus, being able to destroy and rebuild your entire k8s cluster in 30s is wonderful for local testing.
Edit: typos
Honestly, k8s is super easy and very lightweight to run locally if you know the rights tools. There are a few good options but I prefer k3d. I can install Docker/k3d and also build a local cluster running in maybe 2 minutes. It’s excellent for local dev. Even good for production in some niche scenarios
Awesome. Also be sure to use a vpn and and extension to randomize your browser fingerprint!
Well this is legit. I recently cancelled my kagi subscription for privacy reasons. This might make me reconsider. Is anyone here with access willing to test it out and report back?
I expect someone will start a business to remove that aftermarket
I get that he earns money from people watching the video. But 26 minutes is pretty rough when I really just want a text dump of the results. Did anyone spot a list somewhere?
There’s cryptpad though I don’t have a clue how complicated it is to manage. But it’s a decent user experience.
Oh I forgot to mention this part. They have a free demo on Steam with ~1/3 of the playable content. That alone is great. The full game is reasonably priced too and they’re still rolling out content updates frequently