All tools / DevOps & infrastructure
Kubernetes YAML templates
Pick a service, adjust the settings, and copy manifests with persistent storage, Secrets, health checks and resource limits already in place.
Common questions
Are these templates production-ready?
They follow good defaults: persistent volumes, credentials in Secrets, readiness and liveness probes, resource requests and limits, and non-root users where the image supports it. Databases run as a single replica. For high availability, backups and upgrades at scale, use an operator such as CloudNativePG, the MySQL or MongoDB operators, or the kube-prometheus-stack Helm chart.
Which storage class is used?
The cluster's default. Add storageClassName to the volume claims to pick a specific one, such as gp3 on EKS or premium-rwo on GKE.
Why are the image versions pinned?
A pinned tag means every node runs the same version and upgrades happen only when you change it. Update the tag field to the latest release you have tested.
Is my input sent anywhere?
No. The YAML is generated in your browser, and passwords are created with your browser's secure random generator. Passwords are never included in the page address, so share links are safe to send.