Document annotation for namespaces with anyuid enbled

[israel-hdez]

In pull request #18 it was introduced some code to automatically set the UID of the storage-initializer container, so that it runs properly when using Maistra and OpenShift.

For namespaces that forbid running containers with anyuid, the mesh sidecar runs with the project allowed range +1. For namespaces that alloq running containers with anyuid, the mesh sidecar runs with 1337 uid.

The controller always assumes that anyuid is forbidden. So, if the namespace enabled anyuid, the storage-initializer may still fail. However, the end-user can still override which UID is used via an annotation and this can be used as a workaround. Some documentation should state this.

[Xaenalt]

@israel-hdez Is this still needed or has the anyuid fix now made this issue obsolete?

[israel-hdez]

@israel-hdez Is this still needed or has the anyuid fix now made this issue obsolete?

It is still needed for the (corner, for us) use-case of a namespace having the anyuid privilege. If this happens, the user needs to manually add an annotation on the ISVC.

[israel-hdez]

Related upstream PR: kserve#3316.
If the upstream PR is accepted, changes in #18 can be reverted and we can drop this ticket.

cc @ReToCode @skonto

[israel-hdez]

Closing, because kserve#3316 was accepted, and this is no longer needed.