How to use this developer tool
- Paste the requested YAML or key/value input.
- Adjust the available options for the target output.
- Select Generate Secret YAML or press Ctrl/Cmd + Enter.
- Review findings, then copy or download the result.
Create a Kubernetes Secret manifest from KEY=value pairs and choose stringData or base64-encoded data output. Values are processed locally and never submitted by the page. The generator validates metadata and data keys, reports duplicate entries, and clearly distinguishes encoding from encryption so the resulting YAML can be handled with the right security expectations.
Builds an Opaque v1 Secret. In stringData mode values remain readable; in data mode each UTF-8 value is base64 encoded.
The result is generated locally and should be reviewed before deployment.
The Sample button loads a representative input. Running it produces the same structured output displayed in the result panel, including counts and any findings.
DB_USER=appuser DB_PASSWORD=change-me API_TOKEN=test-token
Duplicate keys use the final occurrence. Browser TextEncoder output is converted to base64 safely for Unicode values.
Base64 is not encryption. The generated manifest is visible in page memory and download history; use a secrets manager or sealed/encrypted workflow where required.
The result follows the static rules described on this page. Review finding 1 in context and confirm it with the relevant Docker or Kubernetes command before deployment.
The result follows the static rules described on this page. Review finding 2 in context and confirm it with the relevant Docker or Kubernetes command before deployment.
The result follows the static rules described on this page. Review finding 3 in context and confirm it with the relevant Docker or Kubernetes command before deployment.
Input is processed in your browser. The page does not make a network request with the configuration, but downloaded output and browser history should still be handled according to your security policy.
The result follows the static rules described on this page. Review finding 5 in context and confirm it with the relevant Docker or Kubernetes command before deployment.