I built these for the work I actually do at 2 AM. A Secret that needs to ship before the deploy. A manifest that looks right until kubectl says no. A selector that matches nothing and nobody knows why. Each tool runs here in your browser and gives you a straight answer.
Type your keys and values. I base64 encode them and build a Secret you can apply. Nothing leaves this page.
For a TLS Secret, use the keys tls.crt and tls.key. For basic-auth, use username and password.
Same idea as the Secret, but the values stay in plain text. Good for config files, feature flags, and app settings.
Paste a manifest. I parse it and check the fields kubectl will complain about, line by line. This handles common YAML, not a full parser, so very exotic YAML may need a real cluster check.
Requests times replicas times your unit prices. That is the whole math. Change the prices to match your cluster bill and the estimate follows.
Defaults are rough public-cloud style numbers, not your bill. Edit the two price fields before you quote anyone.
Paste objects, write a selector, see which objects match. This is the fastest way to find out why a Service has no endpoints.
Expressions supported: key in (a, b), key notin (a, b), key exists, key !exists, key = value, key != value.
Paste two values files. I list every key that was added, removed, or changed, with the old and new value. Handy before a helm upgrade.
Paste a small template and its values. I substitute {{ .Values.x }} the way Helm would, so you can spot a wrong key before you render a chart.
Supports {{ .Values.a.b }}, {{ .Values.x | default "fallback" }}, and {{ .Values.x | quote }}. Missing keys are left in place and listed, not silently blanked.