Why is last applied configuration stored as an annotation rather than a seperate object in etcd?

Hi all,

I am very recent new comer into the field of K8s and still learning the ropes

I am following through with a course, during which I came across a video that whenever we use kubectl apply, it stores the last applied configuration as an annotation within the live object definition

I was a bit stumped since I thought that it might be stored as a seperate object in etcd. I tried asking Claude and it mentioned several reasons such as no new API calls required, updating the config and updating the last applied config requires just a single write, which makes sense but when I asked it for references, it could not share any and shared that it had inferred this knowledge

So just wanted to confirm that are the points that Claude shared above are the actual reasons or is there something missing

Thanks all !