Assigned
Status Update
Comments
ma...@google.com <ma...@google.com>
kr...@commitsmart.com <kr...@commitsmart.com> #3 Restricted
Restricted
ma...@google.com <ma...@google.com> #4
The request to show an error for AIDL files in the wrong place is documented in 56930
ja...@regnosys.com <ja...@regnosys.com> #5
If anyone else is having this issue, it took me a while to realize the java file gets generated in the build folder.
kr...@commitsmart.com <kr...@commitsmart.com> #6
Wow... so thanks , issue fixed ;)
ja...@regnosys.com <ja...@regnosys.com> #7
Thanks! It's worked! I'm happy)))
Description
After Google upgraded our GKE nodes from 1.30.8-gke.1261000 to 1.30.9-gke.1046000 NFS volumes get mounted randomly on nodes. We have an nfs instance in Filestore and have persistent volumes in our GKE cluster. After the upgrade, this volumes get mounted on the nodes randomly either with read-only or read-write permissions. In the PV the accesMode is ReadWriteMany.
What you expected to happen:
Volumes get mounted with read-write role as this happened so far.
Steps to reproduce:
Other information (workarounds you have tried, documentation consulted, etc):
I put my pod which use this volume on a node wher it is mounted with read-write role.