this post was submitted on 16 Mar 2025
1063 points (99.2% liked)

Technology

66687 readers
4247 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] cley_faye@lemmy.world 13 points 11 hours ago (2 children)

I don't like the approach of piling more things on top of even more things to achieve the same goal as the base, frankly speaking. A "local" kubernetes cluster serve no purpose other than incredible complexity for little to no gain over a mere docker-compose. And a small cluster would work equally well with docker swarm.

A service, even made of multiple parts, should always be described that way. It's easy to move "up" the stack of complexity, if you so desire. Having "have a k8s cluster with helm" working as the base requirement sounds insane to me.

[–] mac@lemm.ee 1 points 16 minutes ago* (last edited 14 minutes ago) (1 children)

Honestly, a lot of the time I don't understand why a lot of businesses use k8s.

At my company especially, we know almost exactly what our traffic will look like from 9am-5pm. We don't really need flexible scaling, yet we still use it because the technology is hyped. Similar to cloud, we certainly don't need to be spending as much as we do, but since everyone else is on or migrating to the cloud, we are as well.

[–] loudwhisper@infosec.pub 1 points 3 minutes ago

Kubernetes is not really meant primarily for scaling. Even kubernetes clusters require autoscaling groups on nodes to support it, for example, or horizontal pod autoscalers, but they are minor features.

The benefits are pooling computing resources and creating effectively a private cloud. Easy replication of applications in case of hardware failure. Single language to deploy applications, network controls, etc.

[–] Lodra@programming.dev 2 points 7 hours ago* (last edited 7 hours ago) (1 children)

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

[–] cley_faye@lemmy.world 1 points 5 hours ago

I won't argue with the ups and downs of each technos, but I recently looked into docker swarms and it was all I expected kubernetes to be, without the hassle. And I could also get a full cluster with services restored from scratch in 30s. But I am obviously biased towards it, too :)