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
Implement DataGather status conditions and status propagation #805
Implement DataGather status conditions and status propagation #805
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ncaak, tremes The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Found one issue but will report it separately. Approving. |
/label qe-approved |
/retest |
/override ci/prow/e2e-gcp-ovn-techpreview |
/test insights-operator-e2e-tests |
@tremes: Overrode contexts on behalf of tremes: ci/prow/e2e-gcp-ovn-techpreview In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/test insights-operator-e2e-tests |
@tremes: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
…ift#805) * Implement DataGather status conditions * propagate status to clusteroperator status * propagate the failed job to the original status controller * Improve as suggested in review
TechPreview only
This implements the status conditions for the new CRD/CR
datagather.insights.openshift.io
. The CRs will have two basic conditions:DataRecorded
- tells whether the Insights data was recorded correctly or notDataUploaded
- tells whether the Insights data was uploaded or notThe status of the last datagather is propagated/copied into the insightsoperator.operator.openshift.io cluster CR.
Categories
Sample Archive
no new data
Documentation
Unit Tests
pkg/controller/periodic/periodic_test.go
- extendedPrivacy
Yes. There are no sensitive data in the newly collected information.
Changelog
Breaking Changes
Yes/No
References
https://issues.redhat.com/browse/???
https://access.redhat.com/solutions/???