One way to handle this is to install dnsmasq, and configure resolving on the host in such a way that .local will use 127.0.0.1 to resolve DNS. Which will then respond with 127.0.0.1. Using the port matching the K3D cluster will then ensure the correct cluster receives the traffic. - Source: dev.to / over 1 year ago

MetalLB needs a pool of IP addresses it can use for the cluster. I reserved 5 IP addresses between 10.0.0.5 and 10.0.0.10, which were not part of my dnsmasq DHCP pool. Assigning IPs outside the DHCP range prevents conflicts with dynamically assigned IPs in the network. A single IP address would have sufficed for my simple set-up, but I plan to add more services to the cluster and I might need distinct IPs for... - Source: dev.to / over 1 year ago

This seems like an improvement over my current solution in that it can keep multiple projects open simultaneously and route to each of them, but does add more complexity to the setup. I'm using Dnsmasq (https://thekelleys.org.uk/dnsmasq/doc.html) to map anything at .lo to the currently running project, like so:

  brew install dnsmasq.

- Source: Hacker News / almost 3 years ago

I would use a simple dns proxy like Blocky if you want adblocking or dnsmasq if you don't. Source: over 3 years ago

The pervious setup was much the same except the lab was under the UDMP without another gateway. I used UnifiOS to create networks(vLANs) and trusted that segregation to work. It did not. As I progressed in my home lab, I went through a few hypervisors and settled on EXSi and vSphere. 100% overkill but that is what labbing is for right? Again progressing through and adding things like windows AD and many Home... Source: almost 4 years ago

If you like that workflow you might love CheepCode[0] which I built specifically to support it! CheepCode connects to Linear and works on tickets as they roll in, submitting PRs to GitHub. [0] https://cheepcode.com. - Source: Hacker News / about 1 year ago