Comment on Fabricked: Misconfiguring Infinity Fabric to Break AMD SEV-SNPparentComments−nine_k3moWhat is your plan when one of the machines needs to be taken offline for repairs? The probability is low, but the downside may be large.−nullpoint4203moTake it down and replace it? Obviously I’d have HA setup between my nodes, with CSI replication.If budget allowed, I’d even spin up another region with DB failover setup too.All the same architecture applies, the only difference is it’s done with K8S yaml instead of the CDK−tardedmeme3moHow would you do that on AWS? They can shut down your VM due to hardware failures on the host. The probability is low, but the impact may be large.−nine_k3mo(1) They will usually notify a few minutes (or hours) in advance, and (2) it would take a few minutes to spin up and set up a new VM to replace the old, without leaving your terminal.−throawayonthe3mohave three of them−nullpoint4203moHaha exactly - or 4 if we’re balling
Comments
What is your plan when one of the machines needs to be taken offline for repairs? The probability is low, but the downside may be large.
Take it down and replace it? Obviously I’d have HA setup between my nodes, with CSI replication.
If budget allowed, I’d even spin up another region with DB failover setup too.
All the same architecture applies, the only difference is it’s done with K8S yaml instead of the CDK
How would you do that on AWS? They can shut down your VM due to hardware failures on the host. The probability is low, but the impact may be large.
(1) They will usually notify a few minutes (or hours) in advance, and (2) it would take a few minutes to spin up and set up a new VM to replace the old, without leaving your terminal.
have three of them
Haha exactly - or 4 if we’re balling