WebCodeIn

Kubernetes ConfigMap Generator

Generate a valid Kubernetes ConfigMap manifest from YAML, JSON, .env, or .properties configuration.

Your configuration is processed locally in your browser and is not uploaded.

Examples:
0 lines0 charsValid
Valid

About this converter

Paste your application configuration and get back a ready-to-apply Kubernetes ConfigMap YAML manifest — correctly quoted, correctly named, and generated entirely in your browser. Need a Secret instead? Switch the output format and WebCodeIn will base64-encode the values as Kubernetes requires.

How it works

  1. Paste your configuration, or drag & drop a file, into the input panel.
  2. Choose the input and output formats — WebCodeIn detects most formats automatically from the content.
  3. Your converted output appears instantly, computed entirely in your browser.
  4. Copy it to your clipboard or download it as a file. Nothing is uploaded at any point.

Supported formats

Input

  • .env
  • .properties (Spring Boot)
  • YAML (incl. Spring Boot, Kubernetes, Docker Compose)
  • JSON
  • TOML
  • INI

Output

  • .env
  • JSON
  • YAML
  • Docker Compose
  • Kubernetes ConfigMap
  • Kubernetes Secret
  • Shell export
  • TypeScript
  • Spring Boot properties

Frequently asked questions

Is the generated YAML a complete, valid ConfigMap manifest?
Yes — it includes apiVersion, kind: ConfigMap, metadata, and a data block with every converted key. You'll typically just need to rename metadata.name to match your deployment.
What about Secrets instead of ConfigMaps?
Select the Kubernetes Secret output format instead. Values are base64-encoded as Kubernetes requires, and WebCodeIn shows a clear warning that base64 is encoding, not encryption — handle the file like you would the raw credentials.
Does it quote numeric-looking values correctly?
Yes. ConfigMap data values are always strings — WebCodeIn automatically quotes values that would otherwise be misread as a number, boolean, or null when the YAML is parsed (e.g. a port number).

Privacy

Conversion runs entirely in your browser using JavaScript — your configuration is never transmitted to our servers just to be converted. We don’t log your input, store it in our database, send it to analytics, or include it in error reports. The only server-side calls this page makes are for anonymous, aggregate usage counters (which format pair was used) and never include your actual configuration or generated output.

Related tools