Assigned
Status Update
Comments
ba...@google.com <ba...@google.com>
ma...@google.com <ma...@google.com> #2
I had the same problem!
I could solve it by putting the .aidl file in an aidl directory.
Look at the attached screenshot to see the project structure.
I could solve it by putting the .aidl file in an aidl directory.
Look at the attached screenshot to see the project structure.
Description
To automatically refresh cluster node condition after its status has changed(the conditions part when using kubectl describe node).
How this might work:
The worker nodes in a cluster are still showing Readonly Filesystem for the previous mounted volumes , but actually they were deleted already.
If applicable, reasons why alternative solutions are not sufficient:
Customer currently can manually refresh the cluster node condition status by rebooting related nodes,however it really takes time in case there are lots of nodes in a cluster.