I have a t-shirt that says “There Is No Cloud, It’s Just Someone Elses’s Computer”, I also have that same quote on a sticker on the laptop I’m writing this on. It’s a good gag and it’s a view I used to subscribe to but it’s not really true. It’s fair to say that public clouds run on someone elses’s computer but that’s a big distinction. There’s a million articles . . .
Since my first tentative steps in to Kubernetes it’s been an interesting journey. For the most part I suspect the most common way to interact with Kubernetes is to use a managed platform through one of the main public cloud players (that’s certainly been my experience), but it doesn’t do a lot to understand the nuts and bolts of the platform. I’d been meaning to try and get stuck in . . .
Immutable Infrastructure became the new buzzword of DevOps teams a few years ago (around the time that Cattle Not Pets became the decisive philosophy of those same teams) and is one that makes perfect sense. In order for Infrastructure as Code mentalities to be properly executed we need to think of infrastructures (and in particular Cloud Infrastructure) less as nodes to be manually configured and more as abstract objects which . . .
I’m just going to throw it out there, I love working with security, cryptography and certificates. it wasn’t always that way and like a lot of people I used to recoil in horror of the idea of having to work with certificates. In my experience that’s not an uncommon scenario to be in, it’s almost a universally loathed task to have to work with certs and it boils down to . . .
As the DevOps movement gathers more and more speed, companies and their engineers are inevitably coming face to face with open source technologies, or at least technologies with a firm foundation in the open source world. For a lot of people this is causing upset, but why exactly? Open Source software seems to have a bit of an image problems, as if it’s the remit of only a past generation . . .
Over the years I’ve encountered the same problem from huge corporations to small businesses when changing a domain name to another registrar. This seemingly innocuous task frequently ends in disaster, particularly when working with a fly-by-night registrar (though the bigger players are often just as guilty, as are private ISPs) and a lack of understanding somewhere along the lines of who holds DNS records is always the killer. The problem that . . .