Create a "subinterface" on the same VLAN?
We have a number of VMs which provide services to other hosts in our cluster (think perhaps, internal DNS or a database service). In our "physical server" environment, we did this as, say:
eth0: 192.168.0.123 - db01
eth0:0 192.168.0.4 - db
This allows us to, at some future date, build (say) db02 as 192.168.0.124, and migrate the subinterface IP when we're ready for the cutover. Doing things that way, we don't need to change any configs anywhere, we're just using DNS to point to "the live server"
What's the "right way" to do this sort of thing in the Linode ecosystem?
1 Reply
CassandraD
Linode Staff
I don't believe this is an option for either our VLANs or VPCs exactly. You may be able to achieve something closer to what you want with another type of internal networking solution, like a VPN.
You can also check out this post to see if it's helpful:
Another option could be to set up your services all as pods within an LKE Cluster. LKE has internal DNS and Networking that is largely automated and you may be able to find a good set up with that product. I wouldn't suggest learning Kubernetes for this as it would be easier to just update your configurations when you need a new database. That said, if it's something you're already familiar with, it could be an option here.
Lastly, you could possibly set up your services to communicate with each other using our regular private IPs. To make the traffic truly private, you could restrict the traffic using a Cloud Firewall. Then you could swap the private IPs when you were ready to introduce the new database.
I'm sure none of these is an ideal solution based on what you're trying to do, so I've made sure we've passed along your idea as a possible feature in our internal tracking system. I can't promise it's something we'll introduce, but I think it's a good idea that others would find useful as well.