Kubernetes
Choose how to read your input, then generate a ConfigMap, an Opaque Secret, ENV or a string map.
Processed in this browser, held only in page memory. Input is not sent in network requests or share links.
The mask covers the result only; input stays visible. Turn masking off to copy or download real values.
YAML extracts values and rebuilds metadata from these options. Base64 is encoding, not encryption.
Input/data: 256 KiB · 1000 keys · output: 1 MiB · UTF-8 text only
Enter text to begin
The ConfigMap generator helps when application settings must move between a local dotenv file and a Kubernetes manifest. A port such as 0080 stays text, while an entire properties file can remain one value instead of becoming dozens of environment variables.
Start with ENV to ConfigMap for assignments, or choose YAML to extract an existing object. The Kubernetes Secret decoder reads data as UTF-8 after Base64 decoding; ConfigMap to ENV checks portable variable names before producing assignments.
The ConfigMap generator builds ordinary data, Base64-encoded Secret data, or Secret stringData from the same text values. The result starts masked; reveal values before copying or downloading the complete output. The mask is only a screen preview, and the original input remains visible.
A properties file may contain equals signs, blank lines and a final newline that belong to one mounted file. File mode stores the complete text under one chosen key. ENV mode instead parses assignments, so the two input choices deliberately produce different key counts.
The file picker reads using the selected mode; a filename does not select a parser. Choose whole-file text for a mounted configuration file, and choose ENV only when each assignment is a separate setting. Replacement is previewed before application.
The generated object uses the current name and optional namespace. These fields do not inherit source metadata. Leave namespace blank to omit it. File keys containing dots work in YAML and JSON but fail the portable ENV naming check.
Changing source text or conversion options disables exports immediately. Automatic conversion waits 350 ms; turn it off to use Convert or Ctrl/Cmd+Enter. Clear, example and file replacement can each be undone once, restoring the previous input and result.
ConfigMap stores text under data. Opaque Secret can use Base64 data or plain stringData. Every generated YAML key and value is quoted, preventing numeric-looking or boolean-looking settings from changing type.
When a Secret has both fields, stringData replaces matching data values. The status reports the number of overrides. Encoded values are validated first, so an invalid Base64 value is not hidden by a later replacement.
File mode preserves the text, including CRLF, Unicode and trailing newlines, under a single key such as application.properties. JSON input also accepts file keys and multiline strings, without flattening nested objects.
Duplicate assignments, invalid names, non-string data and malformed YAML stop conversion. Errors show a source line and column when available. A failed or stale result cannot be exported; a successful result includes all accepted keys.
Select ENV input and ConfigMap output, then set the object name. The parser removes supported dotenv quotes and keeps every value as text. Review the generated data before using it; importing a dotenv file does not create or modify a Kubernetes resource.
data holds Base64 strings. stringData accepts ordinary strings and takes precedence for a matching key when the two are merged. This tool can generate either representation and reads both; stringData is an input convenience, not a stronger protection mechanism.
No. Base64 is reversible encoding. A masked preview also does not encrypt the input or output. Kubernetes Secret confidentiality depends on access controls and cluster configuration; protect the exported file and avoid treating encoded values as safe to publish.
Kubernetes data is a string map. Unquoted 012 or false may be interpreted as a number or boolean by YAML readers. The generator quotes all keys and values, while its YAML input rejects non-string values instead of guessing their intended spelling.
ENV mode makes a key for each parsed assignment. Whole-file mode makes one key whose value is the entire text. Choose whole-file mode for application.properties or a configuration document that will be mounted as a file; equals signs within it are ordinary content.
Repeated keys stop the conversion instead of silently choosing a winner. Supported dotenv quotes affect the parsed value, and comments are discarded. YAML comments and formatting are also discarded. Use whole-file mode when those characters must be retained as file content.
Missing a conversion case?
Use the ConfigMap generator with a small example, compare the entry count, then choose the output your application expects. Reveal values only when you are ready to review and export the current result.