Generate Production-Ready Kubernetes Manifests

Kubernetes Manifest Generator provides step-by-step guidance for creating Deployments, Services, ConfigMaps, Secrets, and PersistentVolumeClaims. It addresses workload execution, network connectivity, application configuration, and persistent storage, alongside naming conventions and Kubernetes practices. Resource limits, health checks, security contexts, and multi-environment deployment design are part of the intended scope.

Use it when defining a new Deployment, exposing a workload through a Service, preparing configuration resources, or specifying storage for a stateful workload. Begin by clarifying the workload goal, constraints, and required inputs. Detailed patterns and examples are handled through the implementation playbook.

The guidance treats manifest fragments as illustrative rather than validated production configurations. Generating files does not authorize applying them, creating debug Pods or load balancers, running migrations, or reading credentials. Missing inputs, permissions, operational boundaries, or success criteria require clarification.

Inputs include the intended workload, target environment, cluster capabilities, and configuration requirements. Outputs are resource manifests and verification steps appropriate to those requirements. Resolve placeholders, pin images, and select APIs and controllers supported by the target cluster. Verify the ServiceAccount, storage choices, secrets, ports, and probes before considering a manifest ready for use.

Confirm the target context and namespace before an authorized operation. A server-side dry run still contacts admission webhooks, so it is not equivalent to purely local file generation. Keep secrets out of Git and logs. ConfigMap or Secret updates used as environment variables do not automatically refresh running processes. Replicas and maxUnavailable settings alone do not guarantee availability, and alternative template variants should not all be applied together.