docs: Update clustermesh example verification steps

[sayboras]

This commit is to update verification command to avoid the need
of passing pod name explicitly, so that it's easier for users to
just copy and paste.

Signed-off-by: Tam Mach tam.mach@isovalent.com

[qmonnet]

Note that we try to backport documentation changes to all relevant supported branches.

[qmonnet]

Oh, looking at f81e8c6, it seems that this was intentional. @bmcustodio can you have a look, please?

[bmcustodio]

I am trying to remember the reason why I left the same definition on both files, but I can't remember. It can probably be removed (to be clear, I am talking about these bits). But I think that the reason indicated in the commit that @qmonnet mentioned is a valid one for us to leave the separate service definition as it is:

This allows for kubectl apply -f-ing the manifest directly in demo material or when users are trying things out. I guess it also allows for making it clearer in the documentation that the users actually must create the service in both clusters for load-balancing between clusters to work, as per the updated instructions.

[sayboras]

This allows for kubectl apply -f-ing the manifest directly in demo material or when users are trying things out. I guess it also allows for making it clearer in the documentation that the users actually must create the service in both clusters for load-balancing between clusters to work, as per the updated instructions.

Thanks, let me reduce the scope of this PR :)