User avatar
pathetic piss kitten @kitten@elizabeth.cat
42m
thank you so much for this
1
0
2
0

User avatar
pathetic piss kitten @kitten@elizabeth.cat
16m
everyone is always hating on k8s but the truth is:

it works

"but it's overkill" don't use everything it offers from the beginning

"but it's too complex" we all start somewhere, and the alternative isn't much easier

"but it's too corporate" um. well. okay, I guess. the same applies to... most software, to be honest, starting with Linux.
4
1
6
0
User avatar
ramona (512 dimensions) @ramona@app.wafrn.net
13m
@kitten

Okay but the thing that really annoys me is that the control plane takes like 6GiB of RAM at idle, which is nothing if you are a corp and have terabytes, but really matters when you are a catgirl with a budget of "I'm not paying for that" :p
1
0
0
0
User avatar
pathetic piss kitten @kitten@elizabeth.cat
11m
@ramona fair, but that's where its modular architecture has a really good advantage. k3s has been quite manageable for me in terms of resource consumption
0
0
0
0
User avatar
erincandescent ⎔ @erincandescent@erincandescent.net
11m
@kitten “but it’s too complex” to serve a web application you need to know 5 object types:
Namespace (the simplest in the world)
Pod
Deployment
Service
Gateway HTTPRoute or legacy Ingress

You should probably understand what a ReplicaSet does but it’s not that complicated

If you need some storage you’ll need to learn a PersistentVolumeClaim

It’s really not
that much. Yeah it’s a bunch of learning but at it’s core it’s only a handful of objects and most of them are inherently necessary
2
1
0
0
User avatar
erincandescent ⎔ @erincandescent@erincandescent.net
7m
@kitten Also very useful:
ConfigMap
Secret

At some point you’ll bump into ServiceAccounts also but you don’t have to start there
0
0
0
0
User avatar
pathetic piss kitten @kitten@elizabeth.cat
7m
@erincandescent you could even skip on Deployment if you really really just want a web application and to not touch it often
1
0
0
0
User avatar
erincandescent ⎔ @erincandescent@erincandescent.net
5m
@kitten I guess you could just create a Pod but I feel like Deployment is a bit of essential complexity you'll want to learn

Plus being able to murderise pods good
0
0
0
0
User avatar
rachael rachael rachael rachael @rachaelspooky@cyberpunk.lol
10m
@kitten or me! "but i dont know what it is"
1
0
0
0
User avatar
pathetic piss kitten @kitten@elizabeth.cat
6m
@rachaelspooky okay that is a fair argument
1
0
0
0
User avatar
rachael rachael rachael rachael @rachaelspooky@cyberpunk.lol
5m
@kitten ive wanted to learn what it is for years but ive never been allowed (by my bad mental health), it's forbidden
0
0
0
0
User avatar
Klaus Frank @agowa338@chaos.social
5m
@kitten

* But it's annoying to deal with.
* It reminds me too much of work.
* It wastes resources with looping the traffic round unnecessarily (in the default configurations that people gravitate to, not the diy clusters). It's often x4 or x5-ing the traffic...
* It breaks E2E visibility with kube-proxy NATing and people constantly forget that when suggesting/writing ratelimiting and policies.
0
0
0
0