Speaker: Andrew Pruski @dbafromthecold, SQL Server DBA, Channel Advisor
Kubernetes has high availability built into it, but the default settings may not be optimal for certain workloads. In this short session we’ll be looking at what happens to pods in Kubernetes when the node that they are running on fails.
When a node goes into a not ready state, Kubernetes by default, will wait for 5 minutes to move any pods running on that node to a new healthy node.
We’ll discuss how this timing can be adjusted and then have a look at this in action!”
One thing I wanted to ask…with PVs on downed node..they don’t move across until that node is brought up or removed from the cluster (tested in both AKS and EKS).
It’s something that has been holding us back from deploying SQL Server on K8s….the only option we’ve found is a third-party tool from Pure Storage called Portworx.
Learn more: cndmday.com/ev...