-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[candi] CSI old mount cleaner #5153
Conversation
Signed-off-by: Andrey Klimentyev <andrey.klimentyev@flant.com>
🟢 Workflow detailsYandex.Cloud-WithoutNAT-Containerd-1.23 - Connection string: 🟢 |
🔴 E2e for yandex-cloud WithoutNAT;containerd;1.23 was failed. Use:
Workflow details (1 job failed)Yandex.Cloud-WithoutNAT-Containerd-1.23 - Connection string: 🔴 |
/e2e/abort yandex-cloud;WithoutNAT;containerd;1.23 5505336462 5505336462-1-con-1-23 /sys/deckhouse-oss/install:pr5153 cloud-user@84.201.156.51 |
/e2e/abort yandex-cloud;WithoutNAT;containerd;1.23 5505336462 5505336462-1-con-1-23 /sys/deckhouse-oss/install:pr5153 cloud-user@84.201.156.5 |
🔴 Workflow details (1 job failed)🔴 |
🟢 Workflow detailsYandex.Cloud-WithoutNAT-Containerd-1.23 - Connection string: 🟢 |
🟢 Workflow detailsYandex.Cloud-WithoutNAT-Containerd-1.25 - Connection string: 🟢 |
...ble/common-steps/node-group/089_manually_unmount_old_csi_mounts_after_kubernetes_1_24.sh.tpl
Outdated
Show resolved
Hide resolved
/e2e/abort yandex-cloud;WithoutNAT;containerd;1.23 5505336462 5505336462-1-con-1-23 /sys/deckhouse-oss/install:pr5153 cloud-user@84.201.156.51 |
🔴 Workflow details (1 job failed)🔴 |
…d_csi_mounts_after_kubernetes_1_24.sh.tpl Co-authored-by: Denys Romanenko <65756796+RomanenkoDenys@users.noreply.github.com> Signed-off-by: Andrey Klimentyev <andrey.klimentyev@flant.com>
🔴 E2e for yandex-cloud WithoutNAT;containerd;1.25 was failed. Use:
Workflow details (1 job failed)Yandex.Cloud-WithoutNAT-Containerd-1.25 - Connection string: 🔴 |
/e2e/abort yandex-cloud;WithoutNAT;containerd;1.25 5529685365 5529685365-1-con-1-25 /sys/deckhouse-oss/install:pr5153 cloud-user@84.201.135.116 |
🟢 Workflow details🟢 |
🟢 Workflow detailsYandex.Cloud-WithoutNAT-Containerd-1.25 - Connection string: 🟢 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Andrey Klimentyev <andrey.klimentyev@flant.com> Co-authored-by: Denys Romanenko <65756796+RomanenkoDenys@users.noreply.github.com>
Cherry pick PR 5180 to the branch release-1.47 successful! |
Description
Cleanup of old CSI mounts that follow pre Kubernetes 1.24 naming convention. Get deployed only on Kubernetes >=1.24 and only if there are any
Closes #5132
Why do we need it, and what problem does it solve?
It enabled successful Pod volume unmounts when upgrading Kubernetes on the go (without draining a Node).
Closes upstream issue: kubernetes/kubernetes#107065
What is the expected result?
When a kubelet reports that it cannot delete a Pod because there is a mount (with path adhering to an old format), parse a log statement an
umount
manually.Checklist
Changelog entries