Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
My recommendation: get a working K8S "cluster": k3s is a good start as it sets up everything (incl. PV, ingress, LB) on a single machine. Now you can concentrate on having your first app in Kubernetes. Once you got that you can build your own K8S cluster or use GKE or similar if you don't want to worry too much about the management part.
You'll quickly find out that you need some persistent storage or some replication for the DB part: that's where you need persistent volumes like Longhorn or an external storage provider mechanism. Like NFS or iSCSI. You don't need PVs for stateless apps and many apps if well done, are stateless. That's how they scale after all.
Related posts
- How to seperate two Raspberry Pi 4 racks into distinct clusters for K8s?
- Diskomator – NVMe-TCP at your fingertips
- Difference between snapshot-cleanup and snapshot-delete in Longhorn recurring job?
- Ask HN: Any of you run Kubernetes clusters in-house?
- Container redundancy with multiple Unraid servers?