Vault cluster uses hardcoded ips

[MattiasGees]

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
The servers in the vault cluster have a hardcoded ip and are always deployed as x.x.x.10. This can cause ip conflicts with other servers that are already deployed in the same subnet.

What you expected to happen:
Use dynamic ips or allocated by AWS

How to reproduce it (as minimally and precisely as possible):

• Create singlecluster with tarmak init
• tarmak cluster apply

Anything else we need to know?:
Originally this was needed for the Consul cluster, because the UID was based on the ip address of the server. That UID was needed to setup the Consul cluster.
Possible steps to fix this are:

• Investigate if Consul can work with dynamic ips
• If yes use that, if no allocate a network interface to nodes and use that instead of fixed ips

Environment:

• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration**:
• Install tools:
• Others: