Somewhere some of these morons saw something about Fetal Maternal Microchimerism where woman were found with male DNA in their brains (and other places) were from their male children and in rarer cases their older male siblings. Morons see "DNA" and think that means semen.

It's the children held in his basement that are in distress

Georgism was big in the 19th century in the US, advocates that way of taxing land https://en.m.wikipedia.org/wiki/Georgism

I knew a girl whose pastor father molested her, also in NC. It blows my mind that there were people who go weekly to hear "moral teachings" from a man who raped his own daughter

You wait a few years until Alex Jones fans harass you and tell you that you're an actor and never had a kid

I'd have it reconnect on pod down/reregister. The problem with trying to use stickiness is that it is for one part of the equation; there is a singular connection back to on premise that the user needs to use, so must be routed to the pod that has it

How to route ingress into specific pod/node in headless service?

I have a situation that proxies an on-premise server to a user client. Since this is a specific connection established (used to pass user requests backwards to the on-premise servers) on a specific pod, if I can route externally and avoid creating distributor pods. Those would take normal randomish load balanced requests, lookup the right backend pod and open a direct connection for both sides, creating layers which creates problems.....

Looking into headless services, my wish is that I can have a publicly accessible lookup service. This service looks up all pods available (max one per node for NodePort headless), decides on one, puts it into a db and answers queries from the on-premise side and user side. For example the server side gets a response, has value "mynode.whatever.internal.dns.etc". I'm hoping I can write an ingress that will take something like

mydomain.com/servicename/mynode/restofurletc
and automatically have it go to the port on mynode. Then the user side would be the same, doing the initial lookup but using urls to directly go to a backend Node where a connection is known to be established.

Is something like this possible, or some other solution that would work in this way? I'm on AKS

So these people commit a crime to unfurl a flag that says "law and order"?

Cops knocked on my door the first time when I didn't even know it was stolen yet. Second time it was gone for a month, then I happened to see it on the street as I was on my motorcycle. Verified it was mine via sticker and I chased the guy a short bit until he went the wrong way on a one way.

Then called the cops, they refused to do anything except tell me I was wrong to try to get it back. Told them ok, you help me get it. They refused and hung up.

Ah yes, after mine was stolen the second time I gave up. Not allowed to have things in DC.

I just walked (at a crossing with a red man). You could a mile down each side on a slow road, and they were just standing there.

I dunno about skinheads specifically, but there was a terrorist white supremacy organization named after al quida translated into English called the base.

They tried to kill some "antifa" and a few cells got caught. They were talking to the FBI but thought they were talking to Hezbollah.

Generally, they want some same race, same religion state and wish to use terrorism to get there, and that's why they hold ISIS al quida in high esteem, that they also want those things.