Skip to content

HTTPProxy ResourceClaims not getting cleaned up #644

Description

@drewr

Recently I created and deleted several HTTPProxys while working on tunnels. After the deletions my quota was still 10/10. Qwen did some investigation and found out the ResourceClaims were still there.

Update https://github.com/orgs/datum-cloud/discussions/245 when addressed.


⚠️ The Bug
No delete events for the 7 orphaned ResourceClaims (httpproxy-tunnel-8r8qj, b4nlx, cpqsj, lbz2f, mwbrl, nwwn7, w4wvg). The quota system's cleanup controller never fired for these.

Meanwhile, at 01:02-01:09, when you created new HTTPProxies, the quota system DID clean up the old ResourceClaims (e.g., httpproxy-tunnel-9nbwq deleted at 01:09:46). This suggests the cleanup only triggers on HTTPProxy creation (to check quota), not on HTTPProxy deletion.

💡 Root Cause Hypothesis
The ClaimCreationPolicy admission webhook creates ResourceClaims on HTTPProxy create, but there's no corresponding cleanup trigger on HTTPProxy delete. The cleanup controller only runs when new ResourceClaims are being created (as part of quota checking), not as a periodic reconciliation of deleted resources.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions