Description of problem (please be detailed as possible and provide log
snippests):
When creating updateservice from web-console:
1) the default updateservice's name is too long which will cause invalidhost issue as following:
# ./oc get route
NAME                                       HOST/PORT     PATH   SERVICES                             PORT            TERMINATION   WILDCARD
updateservice-sample-policy-engine-route   InvalidHost          updateservice-sample-policy-engine   policy-engine   edge/None     None

So if user create a updateservice with default name(updateservice-sample), no policyEngineURI can be available , we'd better to short the default name. Moreover it's better to give a limitation for this name's input from console.

2) there is unnecessary item in updateservice.spec which created automatically when creating osus instance through web-console.
spec:
  foo: bar
  graphDataImage: >-
    jliu-46.mirror-registry.qe.gcp.devcluster.openshift.com:5000/rh-osbs/cincinnati-graph-data-container:1.0
  releases: 'jliu-46.mirror-registry.qe.gcp.devcluster.openshift.com:5000/ocp-release'
  replicas: 1
There is not "foo: bar" item in updateservice api.
https://github.com/openshift/cincinnati-operator/blob/master/api/v1/updateservice_types.go#L11

I think it should be related with the sample file https://github.com/openshift/cincinnati-operator/blob/master/config/samples/updateservice.operator_v1_updateservice.yaml

Version of all relevant components (if applicable):
OSUS operator image: v4.6.0-6


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?
yes

Can this issue reproduce from the UI?
yes

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Create osus instance from web-console after osus operator installed successfully
2.
3.


Actual results:
Default updateservice is too long to get a valid policyEngineURI and the updateserve.spec is not consistent with updateservice api.

Expected results:
The default updateservice's name and spec for example should be updated.

Additional info: