1,000 karma · joined January 7, 2010
https://docs.godotengine.org/en/stable/tutorials/scripting/g...
Registering gdscript.com and boasting about its search ranking is just gross.
https://techcrunch.com/2012/12/05/kevin-systrom-on-pulling-t...
Disabled people represent between 10% and 20% of the world population, and that's not even including those who don't identify as disabled but would nevertheless benefit from more accessible technology. If you've ever adjusted the text size in your browser or enabled captions while watching media, this group includes you.
I'm afraid not. HTTP GET on a collection endpoint (which is the operation represented by the list verb) returns the full object content.
https://kubernetes.io/docs/reference/access-authn-authz/auth...
https://www.businessinsider.com/joe-rogan-podcast-forest-fir...
[1]: https://youtu.be/luM5uobewhA?t=1301
[2]: http://archieml.org/
If any of the containers in a Pod aren't ready, the endpoints controller[2] removes the Endpoint object corresponding to that Pod. ingress-nginx watches these Endpoints objects[3] to determine which Pods it should send traffic to.
Edit: As to your use case, I think you should remove the readiness probe from that one container you don't care about.
[1]: https://kubernetes.io/docs/tasks/configure-pod-container/con...
[2]: https://kubernetes.io/docs/concepts/overview/components/#kub...
[3]: https://kubernetes.github.io/ingress-nginx/user-guide/miscel...
Still sounds like quite the missed opportunity.
YouTube is not even a "privately owned public space" because it isn't legally required to be open to the public.
If you believe video hosting is critical public infrastructure, nationalize it.
I recently logged into my long-dormant DO account to kick the tires on their now-GA managed Kubernetes service and to contribute some CPU cycles to a distributed computing project I'm interested in (not cryptocurrency, I swear).
I first requested and was approved for a droplet limit increase (to 25). I started 20 nodes, deployed my very CPU intensive workload, and 12 hours later my account was locked and my nodes all went NotReady.
I immediately replied to the abuse ticket explaining my usage. 4 days later, my account was unlocked and received the "allow high CPU" flag... but they billed me for the nodes as if they had been running that whole time. I asked for a credit (5 days ago) and they haven't replied yet. Probably a little busy over there right now.
So... I'm not too thrilled with DO. I get that cryptocurrency ruined everything, but this has been a frustrating experience and I'm glad I was only using it for a pet project.