Transpose
Any config format in, Kubernetes ConfigMaps/Secrets out
Start new thread

Transpose - Any config format in, Kubernetes ConfigMaps/Secrets out

by•
Transpose converts between JSON, YAML, CSV, XML, TOML, INI, ENV, and Java .properties — and generates ready-to-use Kubernetes ConfigMaps and Secrets from any of them, with correct stringification and base64 encoding. Try it free in the browser, or call the same engine from your pipeline via a REST API (POST /v1/convert). Free tier: 50 calls, no charge, quick card verification only — no payment. Paid plans start at $19/mo for live pipelines.

Add a comment

Replies

Best
Maker
📌
Hey Product Hunt 👋 I built this after one too many times manually turning a .env file into a Kubernetes Secret by hand, base64-ing each value one at a time. Figured other people hit the exact same friction moving from local dev config to whatever their deploy target actually wants. A few things I cared about getting right: Full TOML support (not just a "common subset" — nested tables, arrays of tables, the works) UTF-8-safe base64 for Secrets (naive btoa() silently mangles non-ASCII values) Format auto-detection that can actually tell INI and TOML apart, since they both use [section] syntax Would genuinely love to hear what format or target you wish it supported — Helm values, Docker Compose, cloud secret managers (AWS Parameter Store, Azure App Config), Terraform .tfvars are all things I'm considering next, roughly in the order people ask for them.