You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 13, 2022. It is now read-only.
When running the function test_replication_controller_apis from dynamic/test_client.py, the test deletes the replication controller, but not the underlying pods. I think this happens because by default the replication controller orphans the pods when deleted, and a solution could be to set the propagation policy to background or foreground.
If you want I can submit a PR here and then also in kubernetes-client/python, because there are replication controller tests in there that suffer from the same issue.
The text was updated successfully, but these errors were encountered:
Thanks for reporting! I didn't expect the default behavior to be orphan the pods :( It would be awesome if you could open PRs in the repos to fix those tests.
When running the function test_replication_controller_apis from dynamic/test_client.py, the test deletes the replication controller, but not the underlying pods. I think this happens because by default the replication controller orphans the pods when deleted, and a solution could be to set the propagation policy to background or foreground.
If you want I can submit a PR here and then also in kubernetes-client/python, because there are replication controller tests in there that suffer from the same issue.
The text was updated successfully, but these errors were encountered: