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
It looks like the FUSE mount will create a weed process on the Host OS, which isn't limited by the resource limits of the pod that uses the mount.
I'm assuming the weed process could be using a decent amount of CPU and memory. Is there anything that could limit the resource usage of the weed process to avoid it from being a noisy neighbor? Or possibly something that the kubernetes scheduler could use to determine if a pod could fit on the node with this weed process?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It looks like the FUSE mount will create a weed process on the Host OS, which isn't limited by the resource limits of the pod that uses the mount.
I'm assuming the weed process could be using a decent amount of CPU and memory. Is there anything that could limit the resource usage of the weed process to avoid it from being a noisy neighbor? Or possibly something that the kubernetes scheduler could use to determine if a pod could fit on the node with this weed process?
Beta Was this translation helpful? Give feedback.
All reactions