HTTPProxy quota limit hit - orphaned ResourceClaims not cleaned up

[drewr]

Summary

Project drewr-y4nd1b is hitting the HTTPProxy quota limit (10 per project), but only 3 HTTPProxies actually exist.

Problem

There are 10 ResourceClaim entries for HTTPProxies, but only 3 actual HTTPProxy resources. The 7 missing HTTPProxies were deleted but left behind orphaned ResourceClaim entries that were never cleaned up.

Current state

HTTPProxies that exist (3):

• draines (141d)
• tunnel-79nsr (12d)
• tunnel-hz2v8 (12d)

Orphaned ResourceClaims (10, only 3 have matching HTTPProxies):

• httpproxy-tunnel-79nsr (True, 12d) — matches
• httpproxy-tunnel-8r8qj (True, 44m) — NO matching HTTPProxy
• httpproxy-tunnel-b4nlx (True, 51m) — NO matching HTTPProxy
• httpproxy-tunnel-cpqsj (True, 47m) — NO matching HTTPProxy
• httpproxy-tunnel-hz2v8 (True, 12d) — matches
• httpproxy-tunnel-lbz2f (True, 43m) — NO matching HTTPProxy
• httpproxy-tunnel-mwbrl (True, 47m) — NO matching HTTPProxy
• httpproxy-tunnel-nwwn7 (True, 44m) — NO matching HTTPProxy
• httpproxy-tunnel-w4wvg (True, 47m) — NO matching HTTPProxy
• httpproxy-tunnel-xnhnb (True, 12d) — matches

AllowanceBucket status:

• LIMIT: 10, ALLOCATED: 10, AVAILABLE: 0, CLAIMS: 10

Impact

Cannot create new HTTPProxies because quota shows as full.

Question

Is there a known mechanism for cleaning up orphaned ResourceClaims?

Project: drewr-y4nd1b (personal-org-30ea0ba6)

[drewr]

Cross-post: milo-os/milo#644