Boundaries in Dev

I've been working with Red Hat's CodeReady Containers and I recently had a networking issue that might not be obvious to all users. Hyper-V assigns your VM to an address space in the 172.x.x.x range.   CRC also assigns, by default, in the 172.30.0.0/16 address space. This all works well unless Windows assigns your VM an address in 172.30.x.x as well.  Then you get a bunch of networking issues where you can't connect outside the cluster.  This means you can't download images, etc. The solution - reboot your PC and restart CRC until you get an address outside the 172.30.x.x range.

CodeReady Containers Red Hat has produced a single-node kubernetes install that can run on a single developer's machine (also known by the acronym CRC).  This allows you to spin up a cluster, administrate it, and install your own software to it in an environment you completely control. To kick the tires, I wanted to do the following: Deploy a dead-simple application with one REST endpoint  Be able to access it from outside the cluster (i.e. figure out ingress using ISTIO, not just the OpenShift automatic route) Use an external build process using Maven and Google Jib (I like the buildpack like way that OpenShift provides, but I wanted to start without depending on all of that magic). Google Jib   In order to get jib to work, I needed two things: I had to go searching for how the registry that is bundled into CRC is exposed.  You can find the route in th...