I am writing sample YAML files that will serve as examples to bring my coworkers on Kubernetes. This is what my very first "Pod + Service" example looks like so far:

apiVersion: v1
kind: Pod
metadata:
  name: foobar
  labels:
    app: foobar
spec:
  containers:
    image: foobar
    name: foobar
    ports:
    - containerPort: 5000
      protocol: TCP
---
apiVersion: v1
kind: Service
metadata:
  name: foobar
spec:
  ports:
  - port: 80
    protocol: TCP
    targetPort: 5000
  selector:
    app: foobar
  type: LoadBalancer

My point being to provide an example as short and as simple as possible, but still fully functional, I was wondering if the service's spec.selector could use the pod name rather than having to define a label which just repeats the name of the pod.

I have searched quite a bit on Kubernetes GitHub issues, StackOverflow and others, but genuinely did not find any answer other than the Labels and Selectors documentation page which seems to imply, by mostly referring to "label selectors", that only labels can be used in all selectors.

I also tried some random things like spec.selector.name = foobar or, inspired by other features of Kubernetes, spec.selector.metadata.name = foobar, but none of those work, obviously (the service can not find any endpoint).

Also, I've come across a lot of manifests that keep repeating that kind of structure for all their declared resources:

name: foobar
labels:
  name: foobar

I really feel that it would make a lot of sense to be able to use any metadata field in selectors. Am I right to assume that it is not currently possible? If so, what is the rationale?