predictably assigning subnets (and IPs) to gitlab-runner.template #1
Description
I'm seemingly unable to force the resulting VM onto a particular network.
When I specify a particular subnet for the value of Subnet1ID, Subnet2ID, or Subnet3ID, I've so far been unable to convince the VM to request an IP on a particular subnet -- in my case, the subnet in question is required so the VM can reach my gitlab install.
I'm very new with cloudformation templates. Is there a particular method of ensuring a predictable order of IPs, Subnets and Interfaces on the debian VM this builds?