Yes, it’s a loan so big that normal personal finance “savings and loans” rules don’t really apply. This loan is 3X EA’s entire revenue, 2X Nintendo’s entire revenue. Basically an entire new game-publisher’s worth of money flowed into the gaming industry to exert dictatorial control over EA. JPMorgan Chase just have to make sure that they get their money back from the EA employees they just helped the Saudis buy.

The $20B was printed by JPMorgan Chase bankers so that Jared Kushner and the Saudis could buy EA at 45% off. In return, the saudis promise that they can siphon $20B from fired workers back to the bankers over the next ~10 years.

Seems like they’re using katacontainers instead of the Linux kernel for the runtime

that’s how science works, if you want to change the discourse, then prove them wrong

I would probably remove python 2 support, it was end of life when the project was started.

I dont think Immich supports turning a normal account into an sso account, though it may be possible with manual database editing.

EU banks are working on it

https://www.ecb.europa.eu/paym/integration/retail/retail_payments_strategy/html/index.en.html

There’s some sort of SEPA instant payments that come into effect this fall, I think, too.

https://www.ecb.europa.eu/paym/integration/retail/instant_payments/html/instant_payments_regulation.en.html

I believe only the controller needs cooling, not the dies.

Kubernetes is great for single nodes! It definitely is more advanced than docker compose, but it’s actually not hard at all if you read through the documentation. It definitely makes running containers easier in the long run.

Here is my git repo for my big Kubernetes cluster at home: https://codeberg.org/jlh/h5b/src/branch/main/argo/custom_applications

It started out as just a NFS server and a Kubernetes server running on Proxmox in 2021.

It’s not going to make a meaningful difference in your threat model and it will cause a lot of hassle for extra configuration and broken docker images, so I wouldn’t bother.

There is some nice tooling for transparent user name spaces coming down the pipeline in Kubernetes which will be a nice 0-effort security upgrade, but if you don’t have the tooling, I would say it’s not worth it.

https://kubernetes.io/docs/concepts/workloads/pods/user-namespaces/

Hetzner Storage box is $20/month for 10tb.

The moving parts could disturb MIMO

There are probably some with sand and other hard minerals, I think Dove had some soaps with aluminum oxide in it?

Being smug over the meanings of words that aren’t ever actually used in a consistent way is even more American.

Um actually, Strawberries are not a berry, it’s a Gameboy, not a Nintendo, and I lick toads. Can you go to the bathroom?

The only thing similar that I have experienced in Europe is the protected food name law, e.g. Champagne and Parmesan, but that’s an EU cultural protectionism law that the US doesn’t actually follow.

https://en.m.wikipedia.org/wiki/Geographical_indications_and_traditional_specialities_in_the_European_Union

Probably not that hard to build a simple flask frontend around it.

Automatically processing files in an S3/WebDAV directory would also be useful.

https://docs.k3s.io/installation/uninstall

There is also a k3s option for Nixos, which removes the security and side-affect risks of running a random bash script installer.

Very true. Each brick you lay upgrades your setup and your skillset. There are very few mistakes in Kubernetes as long as you make sure your state is backed up.

For question 1: You can have multiple resource objects in a single file, each resource object just needs to be separated by ---. The small resource definitions help keep things organized when you’re working with dozens of precisely configured services. It’s a lot more readable than the other solutions out there.

For question 2, unfortunately Docker Compose is much more common than Kubernetes. There are definitely some apps that provide kubernetes documentation, especially Kubernetes operators and enterprise stuff, but Docker-Compose definitely has bigger market share for self-hosted apps. You’ll have to get experienced with turning a docker compose example into deployment+service+pvc.

Kubernetes does take a lot of the headaches out of managing self-hosted clusters though. The self-healing, smart networking, and batteries-included operators for reverse-proxy/database/ACME all save so much hassle and maintenance. Definitely Install ingress-nginx, cert-manager, ArgoCD, and CNPG (in order of difficulty).

Try to write yaml resources yourself instead of fiddling with Helm values.yaml. Usually the developer experience is MUCH nicer.

Feel free to take inspiration/copy from my 500+ container cluster: https://codeberg.org/jlh/h5b/src/branch/main/argo

In my repo, custom_applications are directories with hand-written/copy-pasted yaml files auto-synced via ArgoCD Operator, while external_applications are helm installations, managed via ArgoCD Operator Applications.

helm charts are awful, i didn’t really like cdk8s either tbh. I think the future “package format” might be operators or Crossplane Composite Resources

deleted by creator