kubernetes-patterns

Organize Kubernetes manifests using a Kustomize base and overlays structure under infra/k8s with distinct directories for dev, staging, and prod. This pattern standardizes base configurations and applies environment-specific patches to simplify multi-environment deployments.

Scaffold Kustomize configurations by generating ready-to-use deployment, service, and configmap templates within a base directory. You then create overlays for each environment that apply specific patches, replicas, and resource limits on top of the shared base.

Add validation patterns like HorizontalPodAutoscaler and PodDisruptionBudget by including them in your Kustomize overlays. These patterns ensure your Kubernetes deployments maintain availability and scale automatically based on resource utilization metrics.

Yes, the Kustomize pattern incorporates standard deployment fields including replicas, resource requests, limits, and readiness and liveness probes. These fields are standardized within the base manifests and can be adjusted through environment-specific overlays.

Yes, you can review and adjust existing Kubernetes manifests by restructuring them into a Kustomize base and applying overlays. This approach allows you to patch deployments, services, and configurations across dev, staging, and prod without duplicating the original manifest files.