1,852 karma · joined October 19, 2021
This is one reason I did poorly in school and eventually dropped out. Teachers chose (either independently or by arrangement) to weigh all grades equally, whether they were at the start of the class or the end. So if you did poorly at the start, you might as well give up, you'll never dig yourself out of that hole.
Important to whom, other than themselves in the next election?
Edit: nevermind, I see it hidden in the site's share menu.
That's what happens when you make a collaborative tool invite only and severely limited the number of invites you can send out. What a truly bizarre choice.
lol? This is your reply to people literally begging you to share your story? That other people won't read it? We can't all get the audience we want.
That's exactly the issue. It'd be better for the orchestration system to handle removing the service from the LB in response to a configuration change than to wait for e.g. health checks to fail.
The SIGTERM method means you have to modify every service to accept SIGTERM (no big deal) for some amount of time (fiddly configuration detail) and in the mean time wait for the LB to see the terminating pod's health check fail so it can stop sending it traffic.
If we flipped it around a bit, having the LB remove the traffic before sending a term signal, we could be more assured that poorly behaving pods (pods that die too quickly or too slowly) don't result in user-facing issues.
2) Sure, firing them is your right. I just think it is perfectly acceptable to hold people accountable for their actions even if they felt morally obligated to perform those actions. And I fully support those that choose not to associate themselves with anyone, for any reason.