-
Notifications
You must be signed in to change notification settings - Fork 8
Fix reconciliation logic for existing and deleted objects #89
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
Conversation
This PR addresses two cases: - Controller Restarts: When the controller restarts, it does not handle deletions for removed objects. Specifically, when an object with a deletion timestamp is passed into the Add() method, the deletion process was not handled correctly. - Recreation of Objects: The recreation of objects is not functioning as expected. For example, when an object is created, deleted, and then created again. In this scenario, the object may enter the Update method, where the creation process was not being handled properly. Signed-off-by: Andrei Kvapil <[email protected]>
✅ Deploy Preview for container-object-storage-interface ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
/assign @shanduur |
Signed-off-by: Andrei Kvapil <[email protected]> <!-- Thank you for making a contribution! Here are some tips for you: - Start the PR title with the [label] of Cozystack component: - For system components: [platform], [system], [linstor], [cilium], [kube-ovn], [dashboard], [cluster-api], etc. - For managed apps: [apps], [tenant], [kubernetes], [postgres], [virtual-machine] etc. - For development and maintenance: [tests], [ci], [docs], [maintenance]. - If it's a work in progress, consider creating this PR as a draft. - Don't hesistate to ask for opinion and review in the community chats, even if it's still a draft. - Add the label `backport` if it's a bugfix that needs to be backported to a previous version. --> ## What this PR does This PR updates COSI image and also includes these fixes: - kubernetes-sigs/container-object-storage-interface#89 - kubernetes-sigs/container-object-storage-interface#90 ### Release note <!-- Write a release note: - Explain what has changed internally and for users. - Start with the same [label] as in the PR title - Follow the guidelines at https://github.com/kubernetes/community/blob/master/contributors/guide/release-notes.md. --> ```release-note [objectstorage] Update COSI controller and sidecar ``` <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Introduced automated image building and version injection for the object storage controller, including support for both controller and sidecar images. * Added comprehensive Kubernetes CustomResourceDefinitions (CRDs) for object storage resources, including Bucket, BucketClaim, BucketClass, BucketAccess, and BucketAccessClass. * Added a dedicated namespace and updated resource naming conventions for improved clarity and consistency. * **Bug Fixes** * Improved and unified deletion handling for object storage resources, ensuring proper cleanup and event recording. * **Chores** * Updated configuration and deployment manifests to use new image locations and naming conventions. * Added a configuration file for specifying the controller image used in deployments. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
/ok-to-test |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kvaps, shanduur 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 |
Reimplement kubernetes-retired/container-object-storage-interface-provisioner-sidecar#139
This PR addresses two cases:
Controller Restarts:
When the controller restarts, it does not handle deletions for removed objects.
Specifically, when an object with a deletion timestamp is passed into the Add() method, the deletion process was not handled correctly.
Recreation of Objects:
The recreation of objects is not functioning as expected. For example, when an object is created, deleted, and then created again.
In this scenario, the object may enter the Update method, where the creation process was not being handled properly.
Signed-off-by: Andrei Kvapil [email protected]