Skip to content
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

Mount using K8S Util Mounter #36

Merged
merged 1 commit into from
May 3, 2020
Merged

Mount using K8S Util Mounter #36

merged 1 commit into from
May 3, 2020

Conversation

maennchen
Copy link
Collaborator

@maennchen maennchen commented May 1, 2020

Closes #33

@maennchen maennchen added the enhancement New feature or request label May 1, 2020
@maennchen maennchen self-assigned this May 1, 2020
@maennchen maennchen force-pushed the mounter branch 4 times, most recently from 0bb8365 to c360d2f Compare May 3, 2020 11:56
@maennchen maennchen marked this pull request as ready for review May 3, 2020 11:56
@maennchen maennchen requested a review from ofek May 3, 2020 11:56
@maennchen
Copy link
Collaborator Author

@ofek This does not solve the problem of container restarts. I'm starting to think that this is not possible without changes from K8S itself.

kubernetes/kubernetes#70013

I'll add a MR that kills pods if the filesystem disconnected next since this is the only possibility I see that is viable. (Allthough not nice and I'd consider it a hack)

The reason this MR is here even though it does not solve the problem, is that this is somehow more stable and easier to maintain then what we had before.

This was referenced May 3, 2020
@maennchen maennchen merged commit ad1bdc2 into master May 3, 2020
@maennchen maennchen deleted the mounter branch May 3, 2020 13:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to find PID of fuse mount
2 participants