-
Notifications
You must be signed in to change notification settings - Fork 61
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
OCPBUGS-36357: Replace watches for CO, Proxy and Machine with actual Watches #452
base: master
Are you sure you want to change the base?
Conversation
Readding the watchOCPConfigPullSecret function to allow triggering reconciliation of the provisioning CR.
@elfosardo: This pull request references Jira Issue OCPBUGS-36357, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: elfosardo 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 |
/retest |
2 similar comments
/retest |
/retest |
@elfosardo: The following test failed, say
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-sigs/prow repository. I understand the commands that are listed here. |
|
||
// Watch Secret openshift-config/pull-secret. If this secret changes, we must requeue the provisioning Singleton, | ||
// if it exists. | ||
watchOCPConfigPullSecret := func(ctx context.Context, object client.Object) []reconcile.Request { |
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.
nit: this variable is confusingly named: it's not used just for the pull secret
Looks good to me, but I'd like like @zaneb to have a look. |
Readding the watchOCPConfigPullSecret function to allow triggering reconciliation of the provisioning CR.