We are using CAPMVM through WGE and can not create clusters that have '-' in the name

[LutzLange]

What happened:
[A clear and concise description of what the bug is.]
An request to create a cluster wtih '-' in the name like 'paul-mvm-36' will fail. The initial control plane machine gets deployed, but I can never reach the kubernetes api-server.

What did you expect to happen:
Provisioning should work and it should not matter if we have a '-' in the cluster name or not.

How to reproduce it:
Go to the demo environment and deploy a cluster. Follow the instructions in this doc

Environment:

• capmvm version:0.4.0

[Callisto13]

This is interesting, because for every demo I have used the cluster name mvm-test. If you see this again, could you share the logs for CAPMVM and Flintlock on the target host (or share the location + login info of where I can find logs)?