Please fill in the following information:

Issue description

Question#1 states:

One of your applications needs at least two pods to be running on nodes, even in the
event of a disruption. Which option would ensure that at least two pods are always
running even in the event of a disruption?

The solution indicates:

Set the maxUnavailable parameter to 2, to ensure that at least two pods are always running.

This would be correct if there were 4 or more replicas in total, but what if there were 3 pod replicas?  Then 2 could be unavailable during a disruption leaving only 1 pod running.

I think a better answer would be choice "c"

Set the minAvailable parameter to 2, to ensure that at least two pods are always running

SEE also `oc explain pdb.spec`

  maxUnavailable    <IntOrString>
    An eviction is allowed if at most "maxUnavailable" pods selected by
    "selector" are unavailable after the eviction, i.e. even in absence of the
    evicted pod. For example, one can prevent all voluntary evictions by
    specifying 0. This is a mutually exclusive setting with "minAvailable".

  minAvailable    <IntOrString>
    An eviction is allowed if at least "minAvailable" pods selected by
    "selector" will still be available after the eviction, i.e. even in the
    absence of the evicted pod.  So for example you can prevent all voluntary
    evictions by specifying "100%".