Documents
3
Development
Generate Kubernetes Deployments, Services, Ingresses, ConfigMaps and Secrets with validation.
Start from a Node.js API, Next.js application, FastAPI service or minimal deployment.
Configure the resource name, namespace and number of pod replicas.
Configure the image repository, version tag, pull policy and exposed container port.
Configure CPU and memory scheduling requests and runtime limits.
Configure a restrictive container-level security context.
Configure readiness and liveness checks for the generated Deployment.
Configure how Kubernetes checks whether the container is healthy.
Configure how Kubernetes checks whether the container is healthy.
Add labels and annotations to the generated Kubernetes resources.
Labels help select, group and identify Kubernetes resources.
Annotations store additional non-identifying metadata.
No entries configured.
Add direct environment variables, ConfigMap entries and Secret values.
Values written directly into the container specification.
Non-sensitive configuration stored in a generated ConfigMap.
Sensitive values encoded into a generated Kubernetes Secret.
No entries configured.
Kubernetes Secret values are only Base64-encoded. Base64 is not encryption. Use an external secret manager, sealed secrets or cluster encryption for production credentials.
Expose the generated Deployment through a Kubernetes Service.
Generate an optional Ingress resource for HTTP routing.
Documents
3
Replicas
2
Environment
1
ConfigMap
1
Secrets
0
Readiness
98%
A lightweight review of availability, resources, security and health checks.
Readiness score
98%
namespaceConsider a dedicated namespace for production workloads.
Review each Kubernetes document independently.
Deployment
bigforgekit-api
Service
bigforgekit-api
ConfigMap
bigforgekit-api-config
Copy or download the complete multi-document YAML manifest.
apiVersion: apps/v1
kind: Deployment
metadata:
name: bigforgekit-api
namespace: default
labels:
app.kubernetes.io/name: "bigforgekit-api"
app.kubernetes.io/component: "api"
spec:
replicas: 2
selector:
matchLabels:
app.kubernetes.io/name: "bigforgekit-api"
template:
metadata:
labels:
app.kubernetes.io/name: "bigforgekit-api"
spec:
containers:
-
name: bigforgekit-api
image: "ghcr.io/example/bigforgekit-api:1.0.0"
imagePullPolicy: IfNotPresent
ports:
- name: http
containerPort: 3000
protocol: TCP
env:
- name: NODE_ENV
value: "production"
- name: CONFIG_MAP_NAME
value: "bigforgekit-api-config"
envFrom:
- configMapRef:
name: bigforgekit-api-config
resources:
requests:
cpu: "100m"
memory: "128Mi"
limits:
cpu: "500m"
memory: "512Mi"
securityContext:
runAsNonRoot: true
readOnlyRootFilesystem: false
allowPrivilegeEscalation: false
runAsUser: 1000
capabilities:
drop:
- "ALL"
readinessProbe:
httpGet:
path: /health
port: 3000
initialDelaySeconds: 5
periodSeconds: 10
timeoutSeconds: 2
failureThreshold: 3
livenessProbe:
httpGet:
path: /health
port: 3000
initialDelaySeconds: 15
periodSeconds: 20
timeoutSeconds: 2
failureThreshold: 3
---
apiVersion: v1
kind: Service
metadata:
name: bigforgekit-api
namespace: default
labels:
app.kubernetes.io/name: "bigforgekit-api"
app.kubernetes.io/component: "api"
spec:
type: ClusterIP
selector:
app.kubernetes.io/name: "bigforgekit-api"
ports:
-
name: http
port: 80
targetPort: 3000
protocol: TCP
---
apiVersion: v1
kind: ConfigMap
metadata:
name: bigforgekit-api-config
namespace: default
labels:
app.kubernetes.io/name: "bigforgekit-api"
app.kubernetes.io/component: "api"
data:
LOG_LEVEL: "info"Apply, inspect, follow logs and delete the generated resources.
kubectl apply -f bigforgekit-api-kubernetes.yaml
kubectl rollout status deployment/bigforgekit-api -n default
kubectl get pods -n default -l app.kubernetes.io/name=bigforgekit-api
kubectl logs -n default deployment/bigforgekit-api -f
kubectl describe deployment/bigforgekit-api -n default
kubectl delete -f bigforgekit-api-kubernetes.yamlKubernetes manifests are generated locally inside your browser. Review image references, secrets, permissions and cluster-specific settings before applying them.
About this tool
Kubernetes Manifest Builder creates a complete multi-document YAML manifest through a structured editor. Configure container images, replicas, resources, security, probes, Services, Ingresses, ConfigMaps and Secrets while reviewing common deployment risks.
Features
Frequently asked questions
It generates a Deployment and can optionally include a Service, Ingress, ConfigMap and Secret.
No. Kubernetes Secret values in the generated manifest are Base64-encoded, not encrypted.
It is a lightweight score based on image versioning, resources, probes, replicas and container security settings.
Yes. Select NodePort and enter a port from the cluster's configured range.
Yes. Enable Ingress and TLS, then enter the hostname and the name of the Kubernetes TLS Secret.
No. It only generates YAML and example kubectl commands locally.
Related tools
Development
Analyze Dockerfiles, inspect build stages and detect common image issues.
Development
Convert docker run commands into Docker Compose YAML.
Development
Generate Nginx reverse proxy configurations with TLS, WebSocket support and security headers.