I'm looking for insights on hosting Microsoft DHCP on a Kubernetes setup. I currently manage MS DHCP failover servers, and I've been tasked with exploring alternatives. My Microsoft Technical Account Manager hasn't provided any leads, but I know this community has some innovative thinkers. I understand that I can create a pod with persistent storage, and I believe I might not need a full cluster for this. Is it really as simple as running the DHCP service in a Windows pod?
2 Answers
Honestly, this might be a tough road. Running MS DHCP isn’t straightforward since it’s not built for containerization. If you're being asked to scale down your servers, maybe consider using a server core version of Windows and manage it through RSAT instead of jumping into Kubernetes right away.
Before diving into containerizing MS DHCP, I’d suggest considering why you're looking to move. What specific issues are you trying to solve by doing this? It sounds like you're trying to move away from W2K16 and VMs due to budget constraints, but switching to Kubernetes might complicate things.
I hear you! Typically, I just swap out servers without changing IPs during an OS upgrade. But with this shift, I see the need to think outside the box. If Kubernetes aligns with your overall strategy, it's worth investigating other options, even if it doesn’t pan out.
That makes sense. I figured exploring Kubernetes would help prepare me for any tough questions, even if I suspect it's not the right fit here.