.env to Kubernetes Secret Converter
Paste KEY=value lines (or a flat JSON/YAML object) to get a Secret with base64-encoded data, a ConfigMap, or both. Everything is processed in your request only; nothing is stored.
About the .env to Kubernetes Secret Converter
The .env to Kubernetes converter turns KEY=value lines (or a flat JSON or YAML object) into a Secret with base64-encoded data, a ConfigMap, or both. It understands export lines and comments, validates resource names and keys, supports a namespace and Secret type, and can write readable stringData instead of base64.
How to use the .env to Kubernetes Secret Converter
- Paste your .env content.
- Choose Secret, ConfigMap or Both, then set the name, namespace and Secret type.
- Click Generate manifest and copy or download the YAML.
Frequently asked questions
Is a base64 Secret encrypted?
No. Base64 is only an encoding that anyone can reverse. Do not commit the manifest to git; use Sealed Secrets, SOPS or an external secrets operator for real protection.
Which input formats are accepted?
KEY=value lines (with optional export and quotes), and flat JSON or YAML objects. Keys may contain letters, digits, dash, underscore and dot; nested values are skipped with a warning.
Are my data stored when I use the .env to Kubernetes Secret Converter?
The text you submit is processed in memory to produce the result and is not saved. Like any web server, Code Converter logs basic visit data (page, IP address and browser) but never the content you paste. Even so, use placeholder values instead of real production credentials.
Is the .env to Kubernetes Secret Converter free, and can I call it from a script?
It is free and needs no account or signup. The same tool is available as a REST endpoint at POST /api/env-to-k8s; see the API documentation for the fields and examples.