Interesting. I suspected the same would happen to my post if I posted this question there.

You’re probably the person that dredged up every bad thing a person has done in the past…

Well that escalated quickly.

Right, that’s a good point.

So far it’s working quite well, however for a micro-sized instance it’s no surprise. Worst case scenario I can do the same thing as the admins of lemmy.world did: create a dedicated scheduling pod using the same docker image as the normal ones, but exclude it from the Service’s target, so it won’t receive any incoming traffic.

The rest of the pods can then be dedicated to serve traffic with their scheduling functionality disabled.

load balancing is automatic between pods thanks to Services: https://kubernetes.io/docs/concepts/services-networking/