I've been working in tech for about 14 years, mostly in test automation, and I'm transitioning toward DevOps and platform engineering. My current work involves GitLab CI/CD, Terraform, Helm, Kubernetes deployments, and some AWS. I'm also leading a migration of many services onto Kubernetes.
The weak spot is Linux. I work at a .NET and Windows-heavy company, so I haven't used Linux seriously in years. I recently tried a basic self-assessment covering systemctl and journalctl, checking which process owns a port, disk usage, apt, and file permissions. I generally knew what kind of tool I needed, but I often couldn't remember the commands.
My employer covers certification costs. I'm currently considering KCNA, CKA, Terraform Associate, and AWS Solutions Architect Associate. I had planned to refresh Linux through a course, use WSL regularly, and build a small homelab rather than pursue a Linux certification.
For people working in cloud, DevOps, or platform engineering: is LFCS, RHCSA, or Linux+ worth adding, or would the CKA and hands-on practice provide enough of a Linux signal? If a Linux certification is worthwhile, which one would you choose and would you take it before or after the CKA? Also, for anyone coming from a Windows-heavy background, what helped your Linux skills become automatic when your job didn't require daily use? How much Linux do you actually use in a platform role compared with what these certifications test? Honest opinions are welcome.
4 Answers
Linux proficiency is more important than the credential itself. In a platform role you may not administer bare-metal servers all day, but you’ll regularly need to understand processes, filesystems, networking, permissions, system logs, containers, and resource limits when something breaks. The certification exercises may be more traditional than your eventual job, but they build the mental model needed to diagnose issues beneath Kubernetes and cloud services.
You definitely need solid Linux fundamentals for DevOps and platform work. Kubernetes and containers are built on Linux concepts, and understanding the underlying system makes troubleshooting much easier. A certification may not be required for most jobs, but a hands-on exam can force you to build real skills. RHCSA is a strong option because it tests practical tasks rather than memorized multiple-choice answers. LFCS is also useful. Linux+ is generally less valuable unless a particular employer or government contract asks for it. After Linux basics, Ansible can be useful too, but the priority should be becoming comfortable with the Linux system itself.
Your proposed path is reasonable, and you don’t necessarily need to add another exam immediately. Use WSL or a small virtual-machine lab every day and deliberately practice users, permissions, services, logs, networking, storage, package management, SSH, and basic shell scripting. The `apropos` command, man pages, and quick reference notes are perfectly normal ways to fill in command gaps. A lab is excellent for Linux fundamentals, while your certifications and work project can cover Kubernetes and cloud skills.
If your employer is paying and you want a structured practical challenge, LFCS or RHCSA makes more sense than Linux+. RHCSA is especially good if you’re comfortable learning the Red Hat ecosystem, even if your workplace uses another distribution. I’d get enough Linux practice first to avoid treating the exam as a memorization exercise, then decide whether to take it before or after the CKA based on which gap is currently slowing you down.
I’d put Kubernetes ahead of traditional configuration-management tools for current platform roles. Ansible can still be useful, but it shouldn’t displace hands-on Kubernetes and cloud practice in the learning plan.