- Malcolm XML
- Aug 8, 2009
-
I always knew it would end like ｔｈｉｓ．
|
It's a bunch of windows services and asp.net sites tied to a big ol' self-hosted sql server instance. Maybe you could host it in Windows containers, but I was under the impression that k8s is really a linux game.
lmao why the gently caress would you do that on k8s. it's not magic that automatically makes ur app scalable
|
#
¿
Dec 23, 2019 19:10
|
|
- Adbot
-
ADBOT LOVES YOU
|
|
|
#
¿
May 8, 2024 09:52
|
|
- Malcolm XML
- Aug 8, 2009
-
I always knew it would end like ｔｈｉｓ．
|
windows software is perhaps a bit more of a special case, but for us, kubernetes manages to surface a lot of unfortunate shortcuts that didn't cause issues on dedicated VMs. these are probably all more just generic issues with adopting to containerized deployments, but k8s has made those more accessible:
* worker process count is determined based on core count by default. this doesn't work very well if you run on a beefy kubelet with many cores, but only allocate 2-4 CPU to the pod, since the "how many cores?" the program sees is the underlying host's core count. doubly so since these workers all allocate a baseline amount of RAM
* things that assume static IPs are poo poo in general in modern infrastructure, and kubernetes' pod lifecycle model demonstrates this quite well
* we have some temporary directories that default to a directory that also holds some static files. kubernetes makes it easy to do read-only root FS for security purposes, and while we have a setting to move the temporary files elsewhere, it turns out we hardcoded the default location loving everywhere
the largest issue, honestly, is that kubernetes operational experience is in fairly short supply, and there are a lot of people being dragged kicking and screaming into working with it because their higher-ups wanted to implement it (not without good reason, mind you, but in typical modern american corporate fashion, they want to do so without training anyone under arbitrary, too-short timelines). as vendor support for poo poo that runs in and heavily integrates with kubernetes, more than half my time ends up being spent on explaining poo poo that's covered in the kubernetes documentation and reminding people that "kubectl logs" and "kubectl describe" will explain the cause of most of their issues.
fix your app server/java version/whatever to be container-aware and the core/memory poo poo will go away
|
|
#
¿
Dec 23, 2019 19:12
|
|
- Malcolm XML
- Aug 8, 2009
-
I always knew it would end like ｔｈｉｓ．
|
I have a unifi dream machine in my house. it's cool and has lots of options I don't understand. also it has an app
should i get one op
|
|
#
¿
Dec 23, 2019 19:13
|
|
#
¿
Dec 23, 2019 19:10
