Handle hash collision in sandboxclaim_controller

[vicentefb]

In #105 (comment) there's a risk of hash collision. If two SandboxClaims in the same namespace happen to hash to the same value, they will share the same NetworkPolicy.

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle stale

[aditya-shantanu]

/close

Network policy usage changed w.r.t claims and this issue is no longer relevant.

[k8s-ci-robot]

@aditya-shantanu: Closing this issue.

Details

In response to this:

/close

Network policy usage changed w.r.t claims and this issue is no longer relevant.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.