Category
Architecture
Decisions when building SaaS on Kubernetes: tenants, networking, storage.
← Clear filter
ArchitectureHelm charts and their disks: what is left after helm uninstall
A Helm chart often brings its own disks, for example for the database bundled in the chart. Some disappear on uninstall, data and all, others stay around forever. You want to know which before you start.
- Volumes
- Backups
- Kubernetes
ArchitectureFrom ingress-nginx to Envoy Gateway: switching controllers without a dark window
Change the ingress class and deploy: the new controller serves, the old one no longer does, and DNS still points at the old one. The host answers 404 until the TTL expires. Here’s a better way.
- Ingress
- Kubernetes
- TLS
ArchitecturePersistent volumes on Kubernetes: ReadWriteOnce, Recreate and the snapshot before deletion
A rolling update with a volume is a deadlock waiting to happen. And deleting a volume from the manifest is data loss waiting to happen. Five rules that prevent both.
- Volumes
- Kubernetes
- Backups
ArchitectureMulti-tenant SaaS: a namespace per customer or a row per customer?
Multi-tenancy is not a yes-or-no question. Most SaaS vendors need both: rows for the many small customers and namespaces for the few large ones.
- SaaS
- Multi-tenant
- Kubernetes