-
Notifications
You must be signed in to change notification settings - Fork 562
[release-4.7] Bug 1972075: Add OperatorCondition status sync and update operator upgradeable check #2206
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
[release-4.7] Bug 1972075: Add OperatorCondition status sync and update operator upgradeable check #2206
Conversation
OperatorCondition controller will update its status to refect the changes on its spec regarding the operator conditions that are reported by the operators themselves. In turn, operators can read the status to confirm if OLM has processed the spec changes. OLM will not take actions on upgradeable condition if the status is stale using ObservedGeneration and Generation check. Signed-off-by: Vu Dinh <[email protected]>
1. Operator can create/update/patch OperatorCondition but not its status. 2. Update the e2e test case to update OperatorCondition's spec directly instead of its status Signed-off-by: Vu Dinh <[email protected]>
@dinhxuanvu: No Bugzilla bug is referenced in the title of this pull request. 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. |
@dinhxuanvu: No Bugzilla bug is referenced in the title of this pull request. 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. |
@dinhxuanvu: This pull request references Bugzilla bug 1972075, which is invalid:
Comment 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. |
/retest |
/retest |
6 similar comments
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
1. Update codegen to generate operatorv2 client code 2. Vendor operator-framework/api 0.9.0 3. Adopt the new changes on OperatorCondition API from api repo. 4. Update OperatorCondition v2 references across the codebase 5. Update e2e test case for OperatorCondition Signed-off-by: Vu Dinh <[email protected]>
d3a4ea3
to
97c7bdc
Compare
/lgtm |
/bugzilla refresh |
@dinhxuanvu: This pull request references Bugzilla bug 1972075, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 6 validation(s) were run on this bug
Requesting review from QA contact: 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. |
@openshift-ci[bot]: GitHub didn't allow me to request PR reviews from the following users: jianzhangbjz. Note that only operator-framework members and repo collaborators can review this PR, and authors cannot review their own PRs. 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. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dinhxuanvu, kevinrizza 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 |
@dinhxuanvu: All pull requests linked via external trackers have merged: Bugzilla bug 1972075 has been moved to the MODIFIED state. 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. |
Description of the change:
OperatorCondition controller will update its status to reflect the
changes on its spec regarding the operator conditions that are reported
by the operators themselves. In turn, operators can read the status
to confirm if OLM has processed the spec changes.
OLM will not take actions on upgradeable condition if the status is
stale using ObservedGeneration and Generation check.
Signed-off-by: Vu Dinh [email protected]
Motivation for the change:
Reviewer Checklist
/doc