jkube.enricher.jkube-service.name is not working when providing fragments

[manusa]

Description

When trying to override the service name using the Enricher configuration, if a fragment is provided, then the name is ignored.

Other enrichers affected

• DefaultControllerEnricher
  Not really affected since this enricher is only applicable when no Controller resources exist (i.e. it's skipped if a fragment exists)
• ControllerViaPluginConfigurationEnricher
• RouteEnricher

Discussion context

I tried to override the
jkube.enricher.jkube-name.name or the jkube.enricher.jkube-service.name properties separately . The first one really changed the name of the deployment name and the service name in the yaml file , and the second did not change the name of service name in the yaml file.

Originally posted by @maodia in #2342 (comment)

[manusa]

Hi @maodia,

The latest snapshot release contains the fix for your issue, could you please try it out and confirm that everything is working as expected?