I don't know if "sorry" is what I'd feel for Hollywood stars like Tom Holland. I'm not sure what I will feel, if at all, but it is probably not close to empathy.
The fact you're trying to tie obesity to alcohol (Existed for thousands of years) and weed is bizarre, considering the far more natural and obvious link is copious amounts of sugar and hfcs (In drinks, spreads, processed food, etc).
A 5 years old kid is not obese because of drugs. He's obese because his parents feed him absolute garbage due to preference, price, eduction, etc.
Most modern/western people are hopelessly addicted to sweet
Don't. Use helm, kustomize or a decent code language.
Dhall will constrict, slow you down, make onboarding a nightmare, and ultimately be as brittle as other alternatives (Only it's harder to find where it broke).
I cannot advocate against dhall enough.
Just my 2cents - ehen I started at current employer, we had a huge, convulted dhall project for kube. We ended up switching to a real language (python in our case due to reasons, Go is a more correct choice) and are very pleased with the results.
I can only recommend aggressively blocking popular subs, ones that are managed by the big mods, and any that have even one political thread that gets a suspicious amount of votes. All actually becomes a source of new interesting content that way.
Don't expect this to change. Most companies realize they can't provide any value for enterprises in that price tier, so they lock SSO behind the most expensive tier. Drives me mad but that's the industry.
Signal has and will go down just like facebook.
Cloudflare/aws having issues affects an insanely high percentage of the internet. People still use them.
Outages rarely cause anything, they happen, people move on.
Not OP, but similar workloads, team of 5
We use kops to deplot and manage the clusters. The hardest part is updating, due to the workloads running on it. Other than that, little to no problems with kube itself.
That's absolutely bullshit, many tech literate people here are against the weapon industry, which NSO is part of. Enough of them don't give a shit, which is why NSO can hire people from the intelligence arm of the army for ridiculous salaries.
Unless I'm mistaken, 100 pulls per 6 hours per IP is a lot - You would/should be caching most of the images from dockerhub anyways, so subsequential builds shouldn't count against your limit.
This was probably the funniest yet interesting and technical talk I've seen recently.
Definitely inspired me to think outside the box and look for these fun things!
I honestly don't understand the amount of negativity towards dockers and kubernetes sometimes.
All major cloud providers have a managed k8 service, so you don't have/need to learn much about the underlying system.
You can spend a few days, at most, to learn about dockers, k8 configuration files and helm and you're pretty much set for simple workloads (and even helm might be overkill).
Afterwards, deploying, testing, reproducing things is, in my opinion, much better than managing your applications on random servers.
Might I be wasting some money on a k8 cluster? Maybe.
Do I believe the benefits outweigh the money? Absolutely.
The hero's journey is the reason I find it so hard to care about anything that happens in Marvel and most fantasy films.
Knowing what comes next (Oh look, here is the part where Thor/Black Panther/Spiderman/etc loses his power) really kills my interest in the plot.
At a previous company, a new employee accidentally commited his aws credentials to a public github repo, which had instance creation capabilities.
It got scraped and we had the max amount of instances created at every zone (we assume for mining).
I assume you have bots scraping public sites for those creds at all times.