Best Kubernetes storage option
Your question is not silly at all, indeed managing WordPress at scale requires broad knowledges due to how WordPress is implemented.
It's good to know that WordPress consists of 1) core PHP code, 2) plugins/themes and 3) uploaded media assets.
To serve the core and plugins, you'll need to locate the code either in local disk or NFS. Local disk is obviously faster since it doesn't interact with network, but NFS is a good choice if you want to have multiple servers to share the same code.
The uploaded media assets are a bit different. The most common &quot;assets&quot; are image files, and you can completely offload the server traffic to object storage such as AWS S3 or GCP Cloud Storage. Unlike plugins and themes, the media assets  are static meaning it will never run server-side logics like PHP.
Moreover, WordPress is read-heavy application that most of the MySQL query is to render blog posts to your public audiences, means any-sized server may blow up when unexpected number of visitors rush to your website. This is where CDN shines, to cache rendered HTMLs in the edge servers at the first visit, then serve the cached files without reaching to origins. AWS CloudFront and GCP Cloud CDN are popular CDNs to turn cheap WordPress server to globally-scalable media site.
So, I recommend to have the following architecture:
Visitor --&gt; CDN --&gt; Web/PHP Server --&gt; MySQL

When configured correctly, you can serve millions of traffics backed with $10 web server.