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

Enable status reporting for CatalogSource in OperatorPolicy #195

Merged

Commits on Feb 9, 2024

  1. Enable status reporting for CatalogSource in OperatorPolicy

    Following the schema of implementing multiple `handle` functions,
    the CatalogSource status reporting logic utilizes the same
    `updateStatus` function to facilitate the `conditions` and
    `relatedObject` field updates on the related operator policy. The
    controller directly checks if the CatalogSource object exists on the
    cluster to propagate relevant health information up to the operator
    policy. The specific field that is checked in the catalog source is
    `.status.connectionState.lastObservedState`. Any value other than
    `READY` is considered as failing.
    
    ref: https://issues.redhat.com/browse/ACM-9285
    Signed-off-by: Jason Zhang <jaszhang@redhat.com>
    zyjjay committed Feb 9, 2024
    Configuration menu
    Copy the full SHA
    90296ff View commit details
    Browse the repository at this point in the history