Fix reconciliation logic for existing and deleted objects

[kvaps]

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kvaps
Once this PR has been reviewed and has the lgtm label, please assign saad-ali for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kvaps]

/assign @saad-ali

[kvaps]

/assign @shanduur

[shanduur]

Hi! Thank you for your pull request. We are in the process of migration towards the monorepo, thus we will no longer accept any PRs to this repository. Please submit your changes to the https://github.com/kubernetes-sigs/container-object-storage-interface-api/tree/monorepo . Thanks!

[kvaps]

Sure done kubernetes-retired/container-object-storage-interface-api#86

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten