Just a heads up, this is only a preview. If you wanted to watch the extended version you will have to get a subscription.
In this episode, we will checking out an IP Geolocation Beta feature using Google Cloud Load Balancers. Using this feature, you can use the Load Balancer to inject user defined HTTP headers with geolocation data from client requests.
Before we dive into the technical aspects of this episode. First, let me show you what the end results looks like. Back in episode 56, we deployed this example site using Kubernetes, then we configured a simple deployment pipeline in episode 58. In this episode, we are adding a little footer down here that guesses where the user request is coming from based off their IP address. You can see here, it says Okay Bay, which is pretty close to where I live. Also, just a heads up, this is pretty specific to Google Cloud but could be reproduced elsewhere with similar technologies (we will about that at the end of this episode).
You can try this out yourself, by going to sysadmindemo.com as looking at the footer. Then, if you click the debug link here, you will get full debug headers of where I think this request is coming from. So, you can see, I think it is coming from Oak Bay, BC, Canada. This is just a few kilometers from my house. Pretty cool.
Alright, lets chat about why I added this? Well, in an upcoming episode, I wanted to build sort of an example interactive game where you answer questions and either get them right or wrong. I wanted to create sort of a leaderboard where we would group all answers by the users country.
Alright, that concludes the preview of this episode. If you want to watch the full version, you will have to have a subscription, you can learn more about them here.