#360 · Developer Tool

Kubernetes Resource Name Checker

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.

Developer Input

YAML or line input

Ad space

How to use this developer tool

  1. Paste the requested names or requirements.
  2. Adjust the available options for the target output.
  3. Select Check Names or press Ctrl/Cmd + Enter.
  4. Review findings, then copy or download the result.

What this developer tool does

Validates one resource name per line, reports length and character violations, and generates lowercase hyphenated suggestions for invalid entries.

DNS subdomains allow lowercase letters, digits, hyphens, and dots with alphanumeric segment edges. DNS labels omit dots and have a 63-character maximum.

The result is generated locally and should be reviewed before deployment.

Example

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

Use cases

  • Pre-commit configuration review
  • Pull request documentation
  • Migration inventory preparation
  • Training and troubleshooting

Tips for reliable output

  • Use spaces instead of tab indentation in YAML.
  • Keep multi-document separators on their own line.
  • Review generated files before applying them.
  • Confirm static findings with official CLI validation.
  • Avoid pasting production secrets into shared devices.

Processing details

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.

Frequently asked questions

Which Kubernetes resource names may contain dots?

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.

Why are uppercase letters and underscores invalid in most resource names?

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.

What is the 63-character DNS label limit used for?

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.

Does metadata.generateName follow exactly the same validation rules?

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.

How are replacement suggestions produced for invalid names?

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.