REGEXVAULTv2.0
Dev & Systems/Config
Verified Safe

Kubernetes Label / Annotation Value Regex for Java

/^[a-zA-Z0-9](?:[a-zA-Z0-9_.\-]{0,61}[a-zA-Z0-9])?$|^$/

What this pattern does

This page provides a well-structured, multi-part regular expression for matching kubernetes label / annotation value, ported and verified for Java. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Java project — whether you're validating in a Spring Boot controller, a Jakarta EE service, or a standalone utility class.

Java Implementation

Java
// Kubernetes Label / Annotation Value
// ReDoS-safe | RegexVault — Dev & Systems > Config

import java.util.regex.Pattern;

public class KubernetesLabelAnnotationValueValidator {
    private static final Pattern PATTERN =
        Pattern.compile("^[a-zA-Z0-9](?:[a-zA-Z0-9_.\\-]{0,61}[a-zA-Z0-9])?$|^$");

    public static boolean validate(String input) {
        return PATTERN.matcher(input).matches();
    }

    // Example
    public static void main(String[] args) {
        System.out.println(validate("production")); // true
    }
}

Test Cases

Matches (Valid)
Rejects (Invalid)
production-start
v1.0.0end-
my-label.dotstart
app_nametoolong----------------------------------------------------------------------------------------------------------
abc-123.xyz

When to use this pattern

This pattern is drawn from the Dev & Systems > Config category and carries a ReDoS-safe certification. That matters for Java developers because critical in Java applications since the JVM regex engine uses backtracking and is susceptible to ReDoS without careful pattern design. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

Kubernetes label keys have a different format: optional prefix (domain.com/) + name, both with their own character constraints. Validate keys and values with separate patterns.

Technical Notes

Label values can be empty (for boolean-style presence checks). Must begin and end with alphanumeric if non-empty. Max 63 chars. Label keys have a separate format (optional prefix/name with different rules).

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.

Submit a Pattern