Thanks for your contribution @log1cb0mb.

I have complicated feelings about this one. In general, I'm not in favor of copying labels or annotations around - I think it's a pretty dirty hack to fit config that should really be stored in a structured field somewhere into labels. But, because we don't have any way to set the settings we want to on the generated Service object, we're kinda stuck with it.

Additionally, we've tried to make this a little more specific with annotations - do you think that we could use a similar mechanism for labels and only copy labels that start with certain strings? I haven't looked at the labels in use for configuring things on Service for some time.

If we agree we want to blindly copy everything, though, the code change itself is fine, but I'd like to see a couple of extra things please?

Firstly, can you update the docs page in Documentation/network/servicemesh/ingress.rst with some information about how all labels will now be copied in addition to annotations?

Secondly, if you could have a look at the tests and see if you can make a test that checks that everything works as expected on the generated Service, that would be awesome. That's a non-blocking request though, so if you would like to merge this first, one of us can either work with you or pick it up to add it later.

So, tl;dr, three things:

• Can you talk a little about copying everything? Would it be okay to use the same logic as the annotations and only copy some labels?
• Please add some docs in the page I mentioned.
• Extra task if you can, but non-blocking, see if you can add some tests?

Thanks again for the contribution, @log1cb0mb, really great to see and well done!

Thanks @log1cb0mb !

changes to ingress re LGTM