aws-efs-csi-driver
aws-efs-csi-driver copied to clipboard
kubernetes-sigs
Removing hostNetwork: true breaks upgrades
/kind bug
What happened?
Upgrading from 1.5.8 to 1.6.0, all of our existing attached storage no longer work.
What you expected to happen? Pods continue to have attached storage.
How to reproduce it (as minimally and precisely as possible)? Deploy 1.5.8 or 1.5.9. Deploy a pod that attaches EFS. Upgrade to 1.6.0.
Anything else we need to know?: If we rollback, things work again.
The one change we do notice is that the CN is different based on the hostNetwork = true/false. You either get the node's hostname or the pod's hostname depending.
Environment
- Kubernetes version (use
kubectl version): - 1.24, 1.26, 1.27
- Driver version: 1.5.8 -> 1.6.0
Please also attach debug logs to help us better diagnose The only thing we notice is that the mount-watchdog.log will kill the stunnel every 5 minutes due to an unhealthy tunnel.
- Instructions to gather debug logs can be found here
