[objectstorage-controller] Update to v0.2.2, drop upstreamed patches - #2261

Walkthrough

The Dockerfile build was simplified (removed git and patch application; COMMIT_REF set to v0.2.2). Two local patches that altered reconciliation and bucket-name derivation were removed, reverting deletion-handling and bucket naming logic to prior behavior.

Changes

Sequence Diagram(s)

sequenceDiagram
    rect rgba(200,200,255,0.5)
    participant K8s as Kubernetes API
    participant Controller as ObjectStorage Controller
    participant Sidecar as ObjectStorage Sidecar
    participant Driver as Storage Driver
    end

    K8s->>Controller: Add/Update BucketClaim/BucketAccess (may have DeletionTimestamp)
    alt Deleted flows were removed (patches deleted)
        Controller->>Controller: handle add/update without early deletion guard
        Controller->>Driver: create/modify bucket or access
    else Prior patched flow (removed)
        Controller->>Controller: detect DeletionTimestamp -> deletion handler
        Controller->>Driver: delete bucket (ignore NotFound)
        Controller->>K8s: remove finalizer / update status
    end

    K8s->>Sidecar: Add/Update Bucket (may have DeletionTimestamp)
    alt Deleted flows were removed (patches deleted)
        Sidecar->>Sidecar: handle add/update without centralized deletion path
        Sidecar->>Driver: create/modify bucket resources
    else Prior patched flow (removed)
        Sidecar->>Sidecar: detect DeletionTimestamp -> handleDeletion
        Sidecar->>Driver: delete bucketAccess / bucket
        Sidecar->>K8s: remove finalizer / update bucket
    end

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 I chewed the patches, nibble by nibble,
COMMIT set, the build made simpler and nimble,
No more diffs to fuss or pry,
Buckets name themselves and drivers sigh,
Hoppity hop—onward we ship and sprout!

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

• X
• Mastodon
• Reddit
• LinkedIn

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.