[kubernetes/kubernetes] Volume manager should not mount the volumes for pods rejected by kubelet (#61137)
Yu-Ju Hong
This came up when I was checking the kubelet logs for #60763
Kubelet admits or rejects pods assigned to the node in its sync loop, and would not start syncing a pod until it's admitted. In the meantime, volume manager works independently to mount volumes for the assigned pods, as long as they are not in a terminated state. This causes issues where kubelet already rejected (or is about to reject) a pod, but their volumes are mounted. The volume manager should wait and check the results of the admission before attempting to mount.
/cc @kubernetes/sig-storage-bugs
/cc @kubernetes/sig-node-bugs
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Hemant Kumar
/remove-lifecycle stale
Hemant Kumar
@yujuhong volume manager uses kubelet's pod manager as source for picking pods that needs volumes. Once a pod gets rejected by kubelet, shouldn't it be removed from pod manager? and in that case - next reconcilliation loop of volume manager should remove the pod from desired state of world.
What do you suggest should be source of truth for volume manager to pick pods from?
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
—
fejta-bot
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
fejta-bot
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
k8s-ci-robot
Closed #61137.
k8s-ci-robot
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
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/test-infra repository.
Hemant Kumar
/reopen
/remove-lifecycle rotten
/lifecycle frozen
Hemant Kumar
This is still a valid bug.
k8s-ci-robot
@gnufied: Reopened this issue.
In response to this:
/reopen
/remove-lifecycle rotten
/lifecycle frozen
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/test-infra repository.
—
k8s-ci-robot
Reopened #61137.
Matthias Bertschy
This bug doesn't seem to have enough details to reproduce or further investigate. You must include your cluster version, the container runtime, kubelet logs, and any relevant Kubernetes manifests along with clear steps to reproduce so we can help with your issue.
Please re-open this bug once you have provided more information.
/triage needs-information
/close
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Kubernetes Prow Robot
Closed #61137.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Kubernetes Prow Robot
@matthyx: Closing this issue.
In response to this:
This bug doesn't seem to have enough details to reproduce or further investigate. You must include your cluster version, the container runtime, kubelet logs, and any relevant Kubernetes manifests along with clear steps to reproduce so we can help with your issue.
Please re-open this bug once you have provided more information.
/triage needs-information
/close
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/test-infra repository.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.