Run Mountpoint inside container #279
Labels
enhancement
New feature or request
Comments
|
Thanks for opening this issue. As I described here, "Running Mountpoint inside a container without any privileges" would be better. How about updating the issue title?? |
|
Hey @everpeace, agree with you. We haven't finalized the design yet, but we aim to make Mountpoint containers unprivileged. |
unexge
added a commit
that referenced
this issue
Nov 22, 2024
This is part of #279. This new component, `aws-s3-csi-mounter`, will be the entry point for the container running Mountpoint. It will be responsible for receiving mount options and FUSE file descriptor and spawning Mountpoint process until completion. --- By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice. --------- Signed-off-by: Burak Varlı <[email protected]>
unexge
added a commit
that referenced
this issue
Dec 16, 2024
This is part of #279. This new component, `aws-s3-csi-controller`, will be the entry point for our controller component. It's using [controller-runtime](https://github.com/kubernetes-sigs/controller-runtime), specifically, it implements [`Reconciler`](https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg#hdr-Reconciler) interface to reconcile Pods in the cluster. It schedules Mountpoint Pods in turn to cluster events such as a new workload Pod using a PV backed by S3 CSI Driver getting scheduled into the cluster. It'd then schedule a Mountpoint Pod for that workload Pod in the same node to provide volume for that Pod. #279 is still WIP and this component contains some TODOs and it's not in use anywhere except in tests at the moment. --- By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice. --------- Signed-off-by: Burak Varlı <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the CSI Driver runs Mountpoint on the underlying host using
systemdvia it's D-Bus API. This approach has some downsides:systemdprocessjournalctlto get Mountpoint logssystemddependency on the host it runsRunning Mountpoint inside a container would help to address these downsides.
The text was updated successfully, but these errors were encountered: