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

Avoid requeueing BundleDeployments that contain the wrong unique provisioner ID #512

Conversation

timflannagan
Copy link
Contributor

Closes #509

@timflannagan timflannagan requested a review from a team as a code owner August 19, 2022 22:58
@timflannagan
Copy link
Contributor Author

The tl;dr was that we were requeueing BundleDeployment resources for both the helm/plain provisioners's BD controllers when encountered a bundle cache event. These changes update this logic to verify that the BundleDeployment that's managing the Bundle also specifies the unique provisioner ID that we are watching to avoid blindly requeueing any BD resource during bundle watch events.

Signed-off-by: timflannagan <timflannagan@gmail.com>
Signed-off-by: timflannagan <timflannagan@gmail.com>
…isioner ID

Signed-off-by: timflannagan <timflannagan@gmail.com>
Signed-off-by: timflannagan <timflannagan@gmail.com>
Signed-off-by: timflannagan <timflannagan@gmail.com>
@timflannagan timflannagan merged commit 448bf42 into operator-framework:main Aug 22, 2022
@timflannagan timflannagan deleted the fix/provisioner-bundledeployment-requeue-logic branch August 22, 2022 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect unique provisioner ID filtering
2 participants