Im asking for someone else here, does anyone have the answer for this: Does any . . .

Kubernetes
#1

Jonathan Tiefer:
im asking for someone else here, does anyone have the answer for this:

Does anyone know what occurs when using required topology spread constraints across <http://topology.kubernetes.io/zone|topology.kubernetes.io/zone> and a zone goes down for network issues? Does the scheduler eliminate the zone from its spread calculations or will the pods that were in that zone now blocked from rescheduling due to being unable to talk to nodes in that zone?

#2

Kosala Atapattu:
There are two options for “whenUnsatisfiable”. I could only get this to work with DoNotSchedule.

#3

Kosala Atapattu:
Else topology restraints are loosely observed… or rather not taken seriously.

#4

Jonathan Tiefer:
thank you Kosala for your response… i will pass this on…

Was surprised that Mumshad never covered this in the CKA course … At least not that I remembered… Maybe this was covered in the CKAD course. i know many things, strangely are not covered in the CKA exam course.

#5

Kosala Atapattu:
This was rather new… IINM, came out in 1.20.xx. So unlikely to be part of CKA/CKAD yet…