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
I also experienced the "transport endpoint is not connected" problem for my k8s cluster and I am unable to umount my mount point from the host. However, I would like to make the recovery process automatically. Here is my trial:
The idea is to umount the fs if it is being mounted before the pod get started. Unfortunately, it doesn't work. Please let us know if anyone has better idea. Thx.
ps:
I also try thinks like the code below or its variation. All trials fail.
I don't have easy access to a k8s cluster -- I know I can create a local one, but that requires some setup. I've marked this with a request for help if someone wants to pick it up. But: could it be because you are using a different user?
Thanks for your help. My initContainers and containers both set privileged as true. I confirm the settings by ssh to the pod, run whoami and get root. So I think both of my initContainers and containers both as the same user. BTW, I also confirm I can the above cmd from my physical host.
ps: I did set UID and GID as another user in env var, but I don't think these env vars are related.
I also experienced the "transport endpoint is not connected" problem for my k8s cluster and I am unable to umount my mount point from the host. However, I would like to make the recovery process automatically. Here is my trial:
The idea is to umount the fs if it is being mounted before the pod get started. Unfortunately, it doesn't work. Please let us know if anyone has better idea. Thx.
ps:
I also try thinks like the code below or its variation. All trials fail.
The text was updated successfully, but these errors were encountered: