Skip to content

docs(jumps): clarify field selector key constraints for resource jumps - #4062

Merged
uozalp merged 1 commit into
derailed:masterfrom
imharjot:docs/resource-jump-fieldselector
Jun 18, 2026
Merged

uozalp merged 1 commit into
derailed:masterfrom
imharjot:docs/resource-jump-fieldselector

Conversation

@imharjot

Copy link
Copy Markdown
Contributor

The Resource Jumps docs imply fieldSelector supports any field, but the selector key is validated by the API server (CRDs only allow declared selectableFields). Clarifies the value-vs-key distinction with a link to the Kubernetes docs. Verified against the code path (no client-side filtering).

Closes #4060

The Resource Jumps docs implied that labelSelector/fieldSelector
templates can reference any field of a resource. The Go template only
controls the selector value, computed from the source resource. The
selector key is validated by the API server against the target
resource. Field selector keys are restricted: most resources only
allow metadata.name/metadata.namespace, and CRDs must declare the
field in spec.versions[].selectableFields, otherwise the API returns
'field label not supported'. Note this distinction and link to the
Kubernetes CRD selectable-fields docs.

@uozalp uozalp left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@imharjot thank you for this update

@uozalp
uozalp merged commit 68e578d into derailed:master Jun 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

custom resource jump fieldseletor docs

2 participants