Hey folks! I've got my K8s interview moved to tomorrow for a senior position, and I'm looking to brush up on a few things. The interview will involve a debugging exercise where I'll be working closely with the interviewer. What are some common problems they might present, and what topics should I focus on in my review? Thanks!
3 Answers
Here are some issues that often come up:
1. Watch out for selector problems; you might end up with a service that has no endpoints due to label mismatches.
2. Check for image pull or mount errors—misconfigured PVs or PVCs can be tricky! Using `kubectl get events` will definitely help you here.
3. Look for scheduling issues, especially if nodes are tainted.
4. DNS problems can arise, so check if CoreDNS is resolving correctly.
5. Don't forget about scaling questions—be ready to discuss HPAs, VPAs, and Karpenter.
Just a note, it’s actually spelled "K8s", not "k8’s"—it stands for 'k' followed by 8 letters and ending with 's'. Some people get really picky about the terminology!
I always start with some basic questions. A lot of interviewees struggle with differentiating between a Deployment and a StatefulSet, so make sure you can explain that clearly. Also, be ready to discuss the kubelet and its role in interacting with the Kubernetes API, as this comes up often!
LOL, I had no idea this would get people so riled up!