[FEATURE REQUEST] Add possibility to provide custom hostnames

Is your feature request related to a problem? Please describe. Currently, there is no option to provide a custom VM hostname via epicli. The hostname is set up referencing inventory hostname.

Describe the solution you’d like Current: [prefix][clustername]-kubernetes[master/node]vm[x] Needed: [prefix][clustername]-kubernetes[master/node]vm[x].[domain.name] but it should allow to set up anything you can imagine 👾

Additional context Internal team request, if possible prepare a workaround they could apply to their LTS deployment.

Please check kind: infrastructure/virtual-machine. Maybe specification.name should be the right place for that? Right now it’s overwritten after manifests merge.

---

DoD checklist

• Changelog updated
• COMPONENTS.md updated / doesn’t need to be updated
• Schema updated / doesn’t need to be updated
• Feature has automated tests
• Automated tests passed (QA pipelines)
  • apply
  • upgrade
• Idempotency tested
• Documentation added / updated / doesn’t need to be updated
• All conversations in PR resolved
• Solution meets requirements and is done according to design doc
• Usage compliant with license
• Backport tasks created / doesn’t need to be backported

[przemyslavic]

@seriva what about adding extra validation for the hostname?

ERROR cli.engine.terraform.TerraformCommand - Error: compute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="InvalidParameter" Message="Linux host name cannot exceed 64 characters in length or contain the following characters: ` ~ ! @ # $ % ^ & * ( ) = + _ [ ] { } \\ | ; : ' \" , < > / ?." Target="computerName"

[przemyslavic]

Tested by @rafzei https://github.com/epiphany-platform/epiphany/pull/2790#issuecomment-1002068421. Thanks man ❤️