How to use this developer tool
- Paste the requested YAML or key/value input.
- Adjust the available options for the target output.
- Select Build Selector or press Ctrl/Cmd + Enter.
- Review findings, then copy or download the result.
Create a Kubernetes label selector from one requirement per line and preview both command-line and structured forms. Use equality, inequality, set membership, exclusion, existence, and non-existence operators. The builder validates label keys and values, removes duplicate set values, and produces a selector string plus matchLabels and matchExpressions YAML where the conversion is unambiguous.
Parses human-editable selector requirements and renders a canonical kubectl selector string together with Kubernetes selector YAML.
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.
app=web environment in (production,staging) tier!=frontend release
Supported forms are key=value, key==value, key!=value, key in (a,b), key notin (a,b), key, and !key. Equality becomes matchLabels; other operators become matchExpressions.
A selector cannot express OR between independent requirements. matchLabels output may be partial when the same key has conflicting equality rules.
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.