15 hours ago · 7 min read1336 words · Tech · hide · 0 comments

Full disclosure, this is one of those posts I do where there’s no dramatic pay off at the end, it’s just documenting something I found that took me a while to figure out and that I thought was interesting :) Understanding the running state of a Kubernetes cluster and its various components, has always been a bit of a tricky affair, with many configuration files and command line flags that need to be read and orders of precedence understood to get the final state. It’s a topic that I’ve had a particular interest in, as I help maintain the CIS benchmark for Kubernetes, and part of that is explaining how to check cluster state in the interest of security hardening. Explaining the different options of where configuration can be loaded from is a bit tricky, so any option for deriving that information easily would be very welcome! A relatively recent development in this space is the official addition of z-pages to various Kubernetes components (although as we see there are some longer…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.