Because I think fast and that intp also matches me.
But I'm honestly thinking this type of categorisation is stupid and doesn't add calue
55 karma · joined March 2, 2023
Because I think fast and that intp also matches me.
But I'm honestly thinking this type of categorisation is stupid and doesn't add calue
What gives?
And no the solution to bulling is not buying hip shit
And why should anyone follow trends just because of some kids?
Wtf what are you a sheep?
Educate your kids to be more independent and think for themselves.
And no I also didn't had always the cool shit as other kids.
No one cares and no it doesn't matter
Anyhow I do remember a post of a person stating this will never happen but it's just a web form and request for describing of what type of research you do
Of course it will be leaked
You need ha because k8s should run already with automatic node upgrades.
You need a pod disruption budget to make sure it is running and switching over when a node fails or gets upgraded.
You want to either totally Oberprovision on memory or look into keep 2400 to make sure to fine-tune memory before k8s starts to throw your database out constantly.
K8s is not a VM.
If you use k8s and still don't take care of application migration strategies you still don't understand what cloud native means.
There are still other things missing here but still...
Of course excluding hobby people playing with k8s.
Memory and upgrading nodes are the two single most issues will see which disrupts service.
Otherwise k8s is a dream come true.
I still would try to use a db managed if it's critical.
Additional points: Zalando postgres operator is great and shows the real magic of k8s and operator.
Use a helm chart and just bring your own little database for dev test and e2e tests.
You can easily use Auto scaling for node profiles. No noisy neighbors. If your db is too small for normal nodes you don't have a problem anyway.