Kubernetes Resource Name (RFC 1123) Regex Pattern

Validates a Kubernetes resource name: lowercase RFC 1123 label, 1-63 chars, alphanumeric + hyphen.

Pattern
^[a-z0-9]([-a-z0-9]{0,61}[a-z0-9])?$

Tested examples

my-app
nginx
pod-123
My-App
-bad
app_v2

Test it live

Live Regex TesterJS
0 matches
/
/g
my-app
nginx
pod-123

Use it in your language

Use it in
// JavaScript / Node.js
const regex = /^[a-z0-9]([-a-z0-9]{0,61}[a-z0-9])?$/;
const value = "my-app";
const isMatch = regex.test(value);
console.log(isMatch); // true / false

// Extract all matches
const matches = value.match(/^[a-z0-9]([-a-z0-9]{0,61}[a-z0-9])?$/g) || [];

Tags

Frequently asked questions

How do I use the Kubernetes Resource Name (RFC 1123) regex pattern in JavaScript?
Wrap the pattern in slashes: const re = /^[a-z0-9]([-a-z0-9]{0,61}[a-z0-9])?$/; — then call re.test(value) to check a single value, or value.match(re) to find matches. The "Use it in" snippets above give you the exact code for 9 languages.
Is this kubernetes resource name (rfc 1123) regex production-ready?
Yes — every pattern in the library is tested against valid and invalid examples. Still, regex is one layer in a defense-in-depth strategy: pair it with server-side validation (e.g. Luhn for credit cards, mod-97 for IBAN, real DNS lookup for emails) for critical inputs.
Why does my pattern fail in another language?
Different regex engines (PCRE, Java, Python, Go's RE2) support slightly different syntax. The most common gotchas: lookbehinds (not in RE2), named groups syntax, and how backslashes need to be escaped inside string literals. The code snippets above already escape correctly for each language.
Can I edit this pattern and test it live?
Yes — use the live tester above. Type your test string and toggle flags (g, i, m, s, u, y) to see matches highlighted instantly, including capture groups.

Related patterns

See all Coding

Browse the full library — 300 tested regex patterns across 16 categories.