ENV to Kubernetes Secret Converter - .env to K8s YAML

Convert .env files to Kubernetes Secrets. Transform environment variables to base64-encoded K8s manifests. Browser-based, private conversion.

.env File Content

Or Upload .env File

Secret Name

Namespace

Use stringData (readable, Kubernetes encodes it)

Kubernetes Secret YAML 0 keys

kubectl Command

kubectl apply -f secret.yaml

Usage in Pod

# Load all as env vars
envFrom:
  - secretRef:
      name: app-secrets

# Or specific keys
env:
  - name: DATABASE_URL
    valueFrom:
      secretKeyRef:
        name: app-secrets
        key: DB_HOST

Batch to Shell Script Converter - Window…

CSV to Markdown Table Converter for GitH…

CSV to Fixed-Width Converter - Positiona…

ICS to JSON Converter - Parse iCal Calen…

LDIF to CSV - Convert LDAP Directory Exp…

View all Data converters →

Frequently Asked Questions

Standard KEY=value format, one per line. Supports quoted values, comments (#), and empty lines. Values with spaces should be quoted: KEY="value with spaces".

Values are base64-encoded for the 'data' field, or kept as plain text for 'stringData'. Kubernetes handles encoding when using stringData.

stringData is more readable and easier to edit. Kubernetes converts it to base64 internally. Use data if you need to store already-encoded values.

Comments (lines starting with #) are ignored in the Secret output. They're used only in .env files for documentation.

Variable expansion (${VAR} or $VAR) is NOT performed. Values are taken literally. Kubernetes doesn't expand variables in Secrets.

Yes, the tool supports bidirectional conversion. Paste a K8s Secret YAML to extract it back to .env format (base64 values are decoded).

Apply with kubectl apply -f secret.yaml. Use envFrom in pod spec to load all keys as environment variables, or mount as volume.

Special characters are handled correctly. Base64 encoding preserves any character. For stringData, YAML special characters may need quoting.

Base64 is encoding, not encryption. Don't commit generated Secrets to Git. Use Sealed Secrets, SOPS, or external secret managers for GitOps.

Yes, you can set metadata like namespace and labels. The converter adds these to the generated YAML manifest.

Related Tools