Open epikjjh opened 2 years ago
Same as #725 . When setting spec: maxUnavailable, the builder can't know the ready state well.
spec: maxUnavailable
gcr.io/cloud-builders/gke-deploy (e.g., gcr.io/cloud-builders/docker)
gcr.io/cloud-builders/docker
Builder should identify that the PodDisruptionBudget is working fine.
PodDisruptionBudget
Even if PodDisruptionBudget is working fine(checked with kubectl), builder identifies this as failure.
Use maxUnavailable then apply the gke-deploy-run
maxUnavailable
At least, we should know maxUnavailable is not supported.
@haroonc I am affected by this bug, do you have any timeline of a fix
Failed to use PodDisruptionBudget
Same as #725 . When setting
spec: maxUnavailable
, the builder can't know the ready state well.Affected builder image
gcr.io/cloud-builders/gke-deploy (e.g.,
gcr.io/cloud-builders/docker
)Expected Behavior
Builder should identify that the
PodDisruptionBudget
is working fine.Actual Behavior
Even if
PodDisruptionBudget
is working fine(checked with kubectl), builder identifies this as failure.Steps to Reproduce the Problem
Use
maxUnavailable
then apply the gke-deploy-runAdditional Info
At least, we should know
maxUnavailable
is not supported.