It depends on your use case, SLA's and configuration management role/structure discipline. There are different schools of thought on diskless boot which is not

It depends on your use case, SLA's and configuration management role/structure discipline. There are different schools of thought on diskless boot which is not truly diskless as the images have to be shared from somewhere meaning that disk availability goes from 1:1 to many to one increasing the blast radius of outages when the NAS fails or network re-convergence occurs. They all fail regardless of how many millions one spends and in my experience the more millions the more glorious the failure that should never happen. For some companies this is fine if they have the discipline to balance their servers across many NAS servers in a strict hierarchy that facilitates a smaller predictable POD structure blast radius. But that's a bigger topic than I could possibly cover in a HN comment. It also depends on how the OS is being used and how writable spaces tmpfs vs disk are being used. This will all vary wildly across different business models.