Network policy fails when completed pods and running pods have the same IP #6507
Labels
area/network-policy
Issues or PRs related to network policies.
kind/bug
Categorizes issue or PR as related to a bug.
reported-by/end-user
Issues reported by end users.
Milestone
Describe the bug
When I have a running pod recycling an IP from a previous completed POD, several times the network policy matches the completed pod , but not the running pod. That leads to communication failure.
To Reproduce
When a cronjob pod completed and another pod created later recycles the IP
Expected
Network policy should work just fine.
Actual behavior
Inconsistent behaviour
Versions:
slack thread
The text was updated successfully, but these errors were encountered: