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.

Sign up for GitHub

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

Jump to bottom

Use DeploymentAvailable instead of custom test for CSV status. #2125

Merged
merged 1 commit into from
Apr 29, 2021
Merged

Use DeploymentAvailable instead of custom test for CSV status. #2125

merged 1 commit into from
Apr 29, 2021

Commits on Apr 29, 2021

  1. Use DeploymentAvailable instead of custom test for CSV status. 

    CSVs can transition to Failed (reason ComponentUnhealthy) if a single
pod managed by one of its deployments is deleted. This commit changes
the deployment availability test from a comparison between
.status.availableReplicas and .status.updatedReplicas to a check that
passes unless the deployment's Available condition exists and is
False.

Signed-off-by: Ben Luddy <bluddy@redhat.com>
    @benluddy
    benluddy committed Apr 29, 2021
    Configuration menu
    Copy the full SHA
    929fa8b View commit details
    Browse the repository at this point in the history