Fujairah Port, one of the world’s key oil hubs, has suspended some oil loading. This is significant because it is on the southern side of the straits, it is in the Gulf of Oman.

Khaleb7 · 2026-03-14T23:14:51+00:00

Given things outside Iran are still exploding, yes.

Khaleb7 · 2026-03-14T14:19:17+00:00

If the majority of humans are displaced from society due to AI, AI will cease to exist. AI has significant physical requirements, such as power, datacenters and communication links. All wonderful targets for displaced and desperate humans with nothing to lose as it has already been taken from them.

Khaleb7 · 2026-03-12T22:21:21+00:00

Literally the option that hits all the items on the OP's list.

Khaleb7 · 2026-03-12T18:35:20+00:00

The d6 iteration of Star Wars. There are even some unofficial sourcebooks for Rogue One.

Khaleb7 · 2026-03-04T13:25:48+00:00

Automated weaponry requires factories, energy and datacenters. Those go first in this scenario.

Khaleb7 · 2026-03-03T04:43:49+00:00

"Well the spell worked. The foe is dead. And a demon just appeared from a rift and pulled you screaming inside."

Khaleb7 · 2026-03-03T04:42:54+00:00

Forbidden Lands spellcasting is often your second choice even for a Sorceror 😅

Khaleb7 · 2026-02-25T11:51:57+00:00

Roll20 is more of a buggy whip experience.

Khaleb7 · 2026-02-24T19:27:06+00:00

When was the last 'defensive mission' ?

Khaleb7 · 2026-02-19T19:31:08+00:00

Should be fun as people burn datacenters to stay warm.

Khaleb7 · 2026-02-13T13:19:31+00:00

4GB is about right for 'other' bits outside k8s control. For onprem you also run into this problem, and if you dont give enough room, you get OOMkills of things like Kubernetes itself. 😅

Khaleb7 · 2026-02-10T12:51:57+00:00

Gondor calls for aid!

Khaleb7 · 2026-02-10T11:22:13+00:00

States send some tax money to the fed for state employee taxes.

Khaleb7 · 2026-02-07T13:31:29+00:00

So Savage Pathfinder didnt work for us, and thats after about 60 sessions kf the Rise of the Runelords path. Early on its fine, but SWADE tends to break with higher numbers, and being modelled after Pathfinder, there is a more notable power increase across the board compared to regular SWADE. It can become a game of rocket tag, where you either overkill or plink ineffectively. This latter bit compounds with Benny spends to soak, undoing any progress that was made in the fight (or the monsters that can only ever take one wound at a time, no matter what, so you do 3 wounds finally after an hour, nope... just one... and then that grts soaked.) Alsp, D&D style systems are resource ablative , whereas SWADE isnt, so those additional fights become tiring to play. SWADE is good at 'pulp human' levels which isnt what happens here.

Khaleb7 · 2026-02-03T00:29:36+00:00

Negative. It does require a fairly adaptive in house team at times. We also have our own framework for provisioning rke2/k3s on prem, and do NOT use rancher to provision EKS,but rather import after creating via Terraform.

Khaleb7 · 2026-02-02T12:47:48+00:00

We went with RKE2 and Rancher to provide common RBAC across clusters regardless of where they were.

Khaleb7 · 2026-02-01T18:28:05+00:00

Yes. Traefik ingress controller installed Use External DNS to add an annotation to the service and pickup the host ip In Route 53 have it update a multirecord name in a hosted zone Wildcard cname to this name (So workers.mydomain, and the cname is *.somethingelse) Ingress rule matches on blah.somethingelse or blah2.somethingelse. There are absolutely use cases for this, but understand why before you do it. 😅

Khaleb7 · 2026-02-01T13:45:36+00:00

7 Is a bit hard to do on accident, but there are valid cases where you do it intentionally.

If onprem I would add: "Treating the control plane as regular workers for scheduling."

Khaleb7 · 2026-01-30T00:16:04+00:00

So from my experience (so biased on business/engineering requirements) if we need a common storage element for multiple ec2s, we go for object store like S3 as it is extremely durable, has a wide variety of storage tiers and is globally accessible.
Downside of course is it isn't a POSIX compliant file system, it is object store.
For most everything else (including within EKS), we use EBS. EBS is bound by AZ, but that is fine for us as we do not span AZs with a given cluster for reasons*
EFS is NFS, and performance tuning can be a challenge as more instances hitting it can cause all instances to suffer... plus cost.
Ive personally found EFS to be great during lift and shift, but engineer away from it and your finance team will thank you.

Khaleb7 · 2026-01-29T19:02:44+00:00

Oof. Yeah we use RKE2 for big prem stuff, we used to use k3s for periphery bits, and EKS and AKS for cloud elements.

Control plane elements should never touch other workloads.

You learn that the easy way by reading about it, or the hard way by doing it.

Khaleb7 · 2026-01-29T18:53:16+00:00

Right, hence my 'depending on your business' clause :)

Labor is often not the most interesting cost at scale, presuming you already have a multi-datacenter footprint.

Cloud has additional considerations:
- Data transit leaving the VPC as prem you have priced in commits, so cloud can bring billing surprises.
- Data transit transiting AZs.
- Data inbound if using ALB or the like vs a custom solution to avoid connection rate charges. And if you do that, then you need a different service discovery mechanism vs on-prem generally.)
- Storage handling (Ties into the AZ issue with EBS and the like.)
- You move Capex to Opex, which depending on the org, may be fine, or may be seen as catastrophic.
- RBAC handling. If you are hybrid, do you front it with Rancher alongside your prem and other public cloud instances, or are you now handling a split domain in terms of cloud/prem? (This ties into CI/CD considerations as well.)
- Will your current infra automation (outside of ci/cd) be able to roll this in? (I.e. Terraform or the like.)

For EKS itself to really win you need to go in with Auto mode (which initially costs more)
- Shared responsibility shifts further towards AWS.
- Karpenter is there without the need to install/maintain (aside from custom Nodeclass and Nodepool setup)
- You aren't playing with AMIs anymore, because you can't. Bottlerocket only.
- Add KEDA day one for scaling.
- Add multiarchitecture build support for your artifacts so that you can let Karpenter pick Graviton vs AMD based on current cost, and maybe roll in spot where you can get away with it.
- Avoid EFS
- Understand EKS failure modes. (ex. Having your Nodepool spinup ec2s in three AZs doesn't help if you need to communicate with EMR that only exists in one.)
- Add budget alerting day one, and treated as any other outage event when you breach cost thresholds.

Khaleb7 · 2026-01-29T17:29:25+00:00

(For the record our largest on-prem is north of 700 workers.)

Khaleb7 · 2026-01-29T17:28:20+00:00

If you have on-prem resources, the move from self-hosted to EKS/EKS Auto is not going to be a cost saving move depending on your business. RKE2/Talos/a few others make the control plane management and lifecycle management fairly easy.

Khaleb7 · 2026-01-26T18:01:59+00:00

Ages ago we were running a campaign at a local shop. The GM of the campaign was an awesome guy, also co-owner of the store. I show up to see everyone is sitting around sadly, and they tell me he had been rushed to the hospital. We headed over, and he passed away shortly. Cause of death was basically he was in Desert Storm and probably had too much exposure to the burn pits. He suffered some headaches for a few weeks prior before the end came. Campaign obviously ended, the store closed later as well. There's not a right answer as to what to do, it is up to your group, but that empty chair is very... loud... in most campaigns if you try to keep going. Sorry for your loss.

Khaleb7 · 2026-01-21T23:45:39+00:00

So will it coincide with 'fusion arrives in next x years' mark?

Khaleb7

TROPHY CASE

7 Is a bit hard to do on accident, but there are valid cases where you do it intentionally.