How to use this developer tool
- Paste the requested names or requirements.
- Adjust the available options for the target output.
- Select Check Names or press Ctrl/Cmd + Enter.
- Review findings, then copy or download the result.
Check a list of proposed Kubernetes resource names against common DNS naming rules. The checker evaluates DNS subdomain and DNS label constraints, shows the exact reason for each failure, and suggests a normalized alternative. Because some resource types impose stricter rules than others, you can switch between the common DNS subdomain rule and the 63-character DNS label rule.
Validates one resource name per line, reports length and character violations, and generates lowercase hyphenated suggestions for invalid entries.
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.
web-api Web_API api.production frontend- worker-01
DNS subdomains allow lowercase letters, digits, hyphens, and dots with alphanumeric segment edges. DNS labels omit dots and have a 63-character maximum.
Kubernetes resource-specific exceptions and generated-name semantics vary by API type. Confirm the chosen kind’s API documentation before deployment.
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.