I'm diving into Kubernetes and looking to set up a quick Hugo blog, but I'm feeling a bit lost when it comes to what kind of storage to use. I have a few specific goals in mind:
- I want my application to be highly available, so I'm steering clear of hostPath volumes, even though they offer simplicity and good performance.
- I need the application data to be easily accessible for backups, and ideally, I want to set up a schedule for regular backups.
- I'm concerned about disk performance and how it might be affected by slow network speeds, especially since I'm running a cluster with nodes in both my homelab and the cloud. However, I'm guessing some compromise may be necessary for high availability.
Any advice you have would be greatly appreciated!
1 Answer
Have you considered using images for your static pages instead of relying on volumes? For stateless workloads, volumes might not be the best approach. This could simplify things a lot for you!
I see what you're getting at, but then I’d need to set up an additional service to handle my custom images. It’s definitely a viable solution, but I'm still leaning towards volumes since I plan to expand into stateful applications later.
Can you break down what you mean by 'building images with static pages'? I'm not entirely familiar with Hugo.