There are many times when you need to get your client IP address: for application telemetry, for getting the client country or any other info you may need. Anyway, when you deploy a .Net Core app on AKS and you are using an NGINX ingress, that you didn’t explicitely configure, the IP address you will be receiving into your app may not be what you expected.

In the previous chapter, we assembled a Docker container to execute a service written in VB6. Today, we are going to use this container in a Kubernetes cluster deployed in Azure using the Azure Kubernetes Service.

Here it is, the first in a series of (4) 5 posts on how to make something new from old Windows Server Applications that you may have running on-premises wasting a lot of hardware and energy.

When you do an assessment of running applications in your Windows servers, as a best scenario, you may find some old web apps running on an IIS server that could be migrated using a semi-automated tool, but, in my experience, there are lots of not-so-edge cases that won’t be as easy as that. Recently, I stumbled on a TCP/IP server application written in VB6 that was running in a few hundred virtual machines. At first, you may think that this application does not deserve the effort and it would be better to do a complete rewrite. Well, on the one side, from a developer or operator point of view you are completely right, but, on the other side, from a business perspective it’s all about trade-offs, and you may not have the budget to build a new app from scratch. So, what if you could reduce the current solution cost by containerizing it, so you save in hardware, and use these savings to push for the rewrite of a new and modern solution? Let’s talk about it.