/assign

/triage accepted

(anyone is welcome to work on this - we have a “no cookie licking” policy in SIG Docs)

If someone has said they plan to work on an issue, and you're also considering that work, it's polite - but not mandatory - to try to co-ordinate.

I did spend time reading materials about this annotation and the PR proposed.
However, I don't think we should add this as a "well-known labels, annotations or taints".
There are a million of annotations/labels used by external tools, but we are not supposed to document them all.

A counter-point to @tengqm is that this annotation is in an official-looking domain, config.kubernetes.io.

There are a million of annotations/labels used by external tools, but we are not supposed to document them all.

The library that uses this annotation is part of the Kubernetes project.

Hi, as there was still discussion on whether this annotation should be registered earlier, can we get a final note on whether working on this Issue and raising PR is required or we can close this issue?

Maybe we can remove triage till the total consensus on this.
If we are open for PR , i can add this one.

Let's treat this as accepted (which is how things stand) until there's consensus to change it.