Allocations present in deleted state post pod deletes

[asm582]

This is not harmful for pod allocations as deleted allocations are reused in the system, when hundreds of pods are deleted we usually see dangling 1 or 2 allocations in the deleted state. This could be the issue with the stale InstaSlice object which needs further investigation. if hundreds of pods are resubmitted the InstaSlice object gets in sync due to churn in the system. Refer this comment: #141 (comment)

[asm582]

PR #184 has addressed this issue and local testing for me shows the same

[kannon92]

/close

#184 seems to mean that this is complete.

[openshift-ci]

@kannon92: Closing this issue.

In response to this:

/close

#184 seems to mean that this is complete.

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.