Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] gke-deploy / PodDisruptionBudget #840

Open
epikjjh opened this issue Jun 7, 2022 · 0 comments
Open

[BUG] gke-deploy / PodDisruptionBudget #840

epikjjh opened this issue Jun 7, 2022 · 0 comments
Assignees
Labels

Comments

@epikjjh
Copy link

epikjjh commented Jun 7, 2022

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-run

Additional Info

At least, we should know maxUnavailable is not supported.

@epikjjh epikjjh added the bug label Jun 7, 2022
@haroonc haroonc assigned haroonc and unassigned plumpy Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants