KubernetesApply step fails if the service name is invalid. As per service spec, service name should have 63 char max and has restricted to certain characters.
In openshift.io, the service name is auto-generated using maven project artifact id and there is no/very less scope to validate the artifacts id/service name upfront if change artifacts id in GH commit.

One solution is to patch the service name on the go in the pipeline using kububernetesApply step. This patching can be enabled or disabled using ENV var. (by default it's disabled).

Is it an acceptable solution?