Bug 1909745

Description of problem (please be detailed as possible and provide log
snippests):
Due to kubernetes pod name length limitation, the prefix automatically added by noobaa to the agent pod of the pv pool name is causing a failure in the pv-pool backing store creation

Version of all relevant components (if applicable):


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?
enter a name shorter than 43 characters

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

Can this issue reproducible?
yes always

Can this issue reproduce from the UI?
yes always

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


Steps to Reproduce:
1. enter the backing store creation tool in the ui
2. create a backing store with a name longer than 43 character 

Actual results:
backing store state is Rejected: Failed connecting all pods in backing store for more than 10 minutes


Expected results:
this should not be allowed, the name of a pv-pool should be limited to 43 both from the UI, Yaml and Cli

Additional info:

***Important note***
The backing store as a resource in Noobaa UI looks ok and the pod,pvc,pv are all created and in state running and bound