pkg/operator Filter out non-MCO CRDs when re-syncing modified MCO CRDs#832
Conversation
kikisdeliveryservice
left a comment
There was a problem hiding this comment.
a couple comments and question
|
aws route 53 errors. /retest |
af3213f to
5ccbfcd
Compare
|
Fixed variable/function naming issues. Trying CI again. |
|
Just double checking, it seems that this requires settling on the proper label (it will depend on whatever is used here: #817 (comment) ) right @runcom @sgreene570 ? |
yep, correct, I will follow up on that. |
|
/retest |
|
strange timeout / monitoring CI errors, trying again. |
|
etcd-quorum-loss is very flaky, so I wouldn't bother retesting for that one @sgreene570 |
|
/skip |
|
putting a hold, since it's pending #817 (comment) resolution /hold |
5ccbfcd to
33c9df6
Compare
|
/test e2e-aws-upgrade |
ae3c504 to
e5eeb94
Compare
|
Applied the proper label from #817 and rebased. |
|
/approve |
|
/retest |
|
@sgreene570 i think you might want to rebase to pick up the latest changes in the repo. i suspect this is why pr is failing. |
|
@sgreene570: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. |
e5eeb94 to
26291bd
Compare
Rebase did the trick, PR is now past the build errors /LGTM |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kikisdeliveryservice, runcom, sgreene570 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fixes #815
- What I did
Following #817, added a label for
mco-built-in/crdto MCO CRDs in themanifests/directory.Then modified
apiExtSharedInformerto filter based on this label.Tested on an AWS cluster to be working.
- How to verify it
Add logging statements to the
enqueuefunction inpkg/operator/operator.goand watchmachine-config-operatorpod logs in kube and verify that non-MCO CRDs are not being re-synced (when they don't need to be, as seen in the issue, #815 ).- Description for the changelog
Filter out object changes not pertaining to MCO when re-syncing MCO CRDs.