At my job, our development environment has changed, and now we have to enter a Kubernetes pod to run our CMS locally. The problem is that the shell experience in the pod is quite bare and frustrating. At home, I usually work with Docker Compose and hardly ever need to enter containers. Is this normal practice for Kubernetes? I've heard I can wrap some commands in my regular shell, but that doesn't seem to fully address the issues. Does anyone have tips on improving the developer experience here, or am I missing something important?
1 Answer
Entering a pod (using exec) is meant just for debugging, not for running services. You typically want to set up your Docker container's entrypoint or command to handle everything automatically. If you're new to this, I'd recommend brushing up on Docker tutorials, especially around entrypoints and commands, then check out Kubernetes resources for pods and deployments. It might seem basic, but knowing these foundations will help you a lot!
I get what you're saying, but I’m not in DevOps - I'm just using what’s been set up. I feel like they might have done it all wrong. I use Docker Compose at home and avoid entering containers unless necessary. With our setup, it feels clunky, especially since we're on WSL which isn't the best. We're doing pretty straightforward actions like starting/stopping clients and copying databases, and I’m wondering if we can alias commands in WSL to run on the pod instead.