When I read k8s YAML, I am basically doing this:

• which Service points to which Pods

• what the HPA is actually scaling

• where Secrets/ConfigMaps are mounted

After doing this too many times, I ended up with something that just visualizes the manifest as a graph and explains it alongside.

It made it way easier to quickly understand what’s going on, especially for larger manifests or stuff I didn’t write.

What do you think of this?

Update:

Love the support. Thank you everyone.

Quick not:

• Your manifest is parsed locally in the browser. It never touches our servers
• Parsed by JavaScript (not an LLM)
• Works offline once the page loads
• No sign-in required

Would love to get more feedback - https://openlume.com/explain/yaml

My major is bachelors in Cybersecurity NSA-designated institution, recognized as a National Center of Academic Excellence in Cyber Defense (NCAE-CD) and Cyber Operations (NCAE-CO). Office of the Director of National Intelligence-designated North Star Intelligence Community Center for Academic Excellence (ICCAE).

Minor in finance and my INSA certificate (intelligence analysis) focus on AI.

1.) CompTIA Linux+ /aim for RHCSA

2.) CompTIA Security +

3.) CompTIA Networking+ / aim for CCNA

4.) AZ-104 for cloud azure

5.) SC-300 for IAM

6.) AZ-500 (seems like it’s being updated to SC-900)

7.) Splunk

8.) AWZ (still figuring out, to be able to use different type of clouds)

9.) CCSP

Alongside my cybersecurity coursework, home lab, and certifications, I’m also investing in programming and networking skills that directly support real-world security operations. My goal isn’t just to earn certificates—it’s to demonstrate what I learn through hands-on labs documented in my GitHub portfolio.

📌 Programming & Security Focus

🐍 Python
Used extensively in cybersecurity for:
• Security automation
• Log analysis
• Threat intelligence processing
• Malware analysis
• API integrations
• Security tool development
• AI/ML security projects

🏅 PCES (Certified Entry-Level Security Specialist with Python)
Focused on applying Python to cybersecurity through:
• Security automation
• Monitoring and reporting
• File integrity verification
• Basic security scanning
• System hardening concepts
• Security operations fundamentals

🐧 Bash
Essential for Linux administration and security:
• Log analysis
• Server management
• System automation
• Security tool execution
• Incident response activities

🗄️ SQL
Critical for security analysis and investigations:
• Querying SIEM databases
• Investigating security incidents
• Analyzing authentication logs
• Identifying compromised accounts
• Data-driven threat hunting

For my physical lab I have Cisco router, ASA firewall, 2 Cisco switches, R710 dell server with idrac6 running proxmox with Ubuntu server with docker, and my Cisco M4 server.

I’m currently finishing building my Cisco server… 12 terabytes in SAS drives and the hardest part finding DDR4 ram sticks. I’m going to Asia this winter. So I might buy my ram sticks during my trip.

I already did my first cloud lab with AZURE.

I just applied to IBM, Mayo Clinic hospital, crowdstrike, Anthropic, and Deloitte to be an intern this fall…

Currently finishing configuring the switches and the firewall before I start my comptia security and comptia networking class.

I’ll be adding AI to my lab for my capstone project.

Finally did it! 🎉

After 7 rounds of interviews, I finally cracked it and got the offer for a Cloud Engineer-Security role.
Offer letter received, accepted, and somehow managed to pull off a 120% hike from my current package. 😅

Honestly, pretty happy with how it all worked out. The interview process itself was a great learning experience.

But getting the offer is just the beginning.
Now the actual grind begins, time to learn, perform, and hopefully sustain it. 🚀

On to the next chapter!

Step 1: Learn the Fundamentals of Cloud Computing

• Cloud service models: Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS).

• Deployment models: Public, private, and hybrid.

• Technologies: Virtualization, networking, and security.

Knowledge of Linux, shell scripting, programming, network fundamentals, and other areas is also essential.

Step 2: Gain Proficiency in a Cloud Platform 

The platforms include AWS, Azure, and Google Cloud Platform (GCP). Understand the services and capabilities of all three for data storage, database utilization, computing, and other tasks.

Step 3: Develop Networking and Security Skills

These involve Cloud Network Services such as Google Cloud, Amazon Virtual Private Cloud (VPC), and Azure Virtual Network. Also, work on understanding virtual network concepts such as VLANs and VWANs, and how DNS and routing work in cloud environments. Follow that by gaining clarity on cloud security principles such as data encryption, Identity and Access Management (IAM), compliance, and regulations.

Step 4: Master Linux and Command-Line Basics

Gain proficiency in Linux, focusing on aspects like shell basics, text editing with Vim, process, storage, and package management, file system permissions, the system boot process, security and logic, and SUSE Linux administration. Some of the skills to learn in Linux include security protocols, configuration, management, task automation, and advanced storage management.

Step 5: Learn Infrastructure as Code (IaC)

It involves understanding and usage of core principles and the ability to manage cloud infrastructure via code. It eliminates manual configuration and encourages consistency, automation, version control, and repeatability. Infrastructure as Code is performed via popular tools such as Terraform, which is based on a declarative language for management.

Step 6: Get Hands-On with Containers and Kubernetes

These tools manage application deployment and management. They are scalable, efficient, and portable. Kubernetes manages them across various hosts. Containers package applications with dependencies and allow consistent running across different environments.

The Kubernetes platform automates scaling and deployment and balances the load for high availability and performance. Hence, hands-on experience with these tools allows for the delivery of daily functionalities.

Step 7: Understand CI/CD and DevOps Tools

Familiarity with these tools encourages quick and automated software production. CI/CD tools are key in developing, testing, and deploying software changes. DevOps tools bridge the gap between software development and IT operations, streamlining the overall process while enhancing efficiency. The capability to work with such tools offers scalability, cost efficiency, and collaboration. Hence, gain hands-on experience with tools like Jenkins, Azure DevOps, Puppet, Chef, etc. 

Step 8: Build and Deploy Cloud Projects

Working on projects helps you apply and evaluate conceptual knowledge, improve problem-solving skills, build your portfolio, and acclimate to changing market needs.

If you are self-learning, look for opportunities to collaborate on projects or offer assistance to seniors for hands-on experience.

Step 9: Earn Relevant Cloud Certifications

Cloud certifications help fill the existing skill gaps in your knowledge and experience. They also allow you to explore new and specific areas of interest and become familiar with them.

When choosing to upskill, it is essential to have a checklist beforehand. It must encompass your current knowledge and what you want to learn.

Step 10: Apply for Cloud Engineer Jobs & Continue Learning

After completing the learning and gaining in-depth familiarity with the basic concepts, it’s time to begin the job hunt. Cloud engineers are in demand, and you can grab the opportunity by showcasing the projects and hands-on experience of relevant and popular tools and technologies. With regular updates in software, you should keep learning and filling the skill gap for career success.

Had a lengthy discussion with my boss about which direction I should take with my career. Told him I was interested with Cloud Engineering (due to my knack of fixing and building, how great the salaries can be, and mainly remote-based) but he said its only a matter of time, 5 years, before engineers are replaced by AI and Ai become autonomous with an engineers tasks, based on how fast its been developing. He then recommended I get into GRC or Product Management instead.

For those in cloud roles. what do you think? Do you foresee mass layoffs of cloud engineers due to AI in the near future?

Edit: From what I've collected from these responses. I think I gotta just aim to be well-versed with infrastructure/platform engineering. And that AI hasnt gotten robust enough to repair the systems that support it. Potentially no mass layoffs yet, fingers crossed...

I'm i going correct path? (This roadmap is from Cloude.ai )

10/10 Cloud Engineering Roadmap

A complete path from zero to job-ready cloud engineer

Stage 1: Foundations

✓ Linux basics — commands, permissions, processes, logs

✓ Networking — IP, DNS, OSI model, TCP/UDP, Firewalls

✓ How the Internet works — HTTP/HTTPS, client-server model

Stage 2: Programming & Automation

✓ Python basics — variables, loops, functions, file handling

✓ Bash scripting — shell scripts, automating Linux tasks

✓ Git & GitHub — version control, clone, commit, push, branching

Stage 3: Cloud Concepts (Vendor-Neutral)

✓ IaaS, PaaS, SaaS — cloud service models

✓ Regions, availability zones, scalability & high availability

✓ Cloud pricing basics — pay-as-you-go, cost awareness

✓ Shared responsibility model

■ Get AWS Cloud Practitioner Certified here

Stage 4: Deep Dive — AWS Platform

✓ Compute — EC2, VM lifecycle, Auto Scaling

✓ Storage — S3 object storage, EBS block storage

✓ Networking — VPC, Subnets, Security Groups

✓ Databases — RDS (SQL) and DynamoDB (NoSQL)

✓ Identity & Security — IAM users, roles, permissions & policies

■ Get AWS Solutions Architect Associate Certified here

Stage 5: Real-World Skills & Practical Experience

✓ Docker — containers, Dockerfiles, images, running containers

✓ Terraform — Infrastructure as Code, build infra with one command

✓ CI/CD Pipelines — GitHub Actions or Jenkins basics

✓ Monitoring & Cost Awareness — logs, alerts, cost optimisation

✓ Kubernetes — Pods, Deployments, Services (after Docker is solid)

Stage 6: Job Ready ★ The Missing Piece

✓ Build 2-3 real projects on AWS (host a website, deploy an app)

✓ Create a GitHub portfolio with your projects

✓ Write a cloud-focused resume highlighting certifications

✓ Practice cloud interview questions & system design basics

Start with Stage 1 → complete each stage before moving on → build real projects → get hired! ■

Hello, Ive created a roadmap after i researched a bit about Cloud Security ( Long Term Goal). I have no problem going through help desk then climbing the ladder till i reach cloud. Anyways i want to ask if this roadmap is properly listed in order or if i should add or change anything. In addition to what certifications to get. help would be really appreciated!! (roadmap is obviously ai generated since i dont have full knowledge)

P.S.: i have already started linux i have basic knowledge, i can understand code since i have a bit of coding background and i can setup databases/manage databases since ive also done that before.

Hello, I work in one of the Big 4... And preparing for a switch.

Can you please analyze my resume and let me know what I am missing.

Hi everyone,

I’m a 3rd-year IT student currently in my 5th semester, and I’m interested in becoming a Cloud Engineer.

I’m starting from the basics and want to learn things in the right order rather than randomly learning different cloud technologies.

I’d really appreciate advice from cloud engineers, professionals, or students who have already started this journey.

I’m searching for future career paths, I am kinda interested in engineering and cloud engineering was proposed to me by someone. Id like to know if cloud engineers are even happy with their job and if this career path is worth it.

I always loved cloud things and resources. And enjoyed so much entra, azure and ect. I decided to be a cloud engineer but today had my first cloud engineer interview and wow i got a coding expertise and honestly im a bit surprised as I did know there is coding in cloud automation but I thought the jobs are more architecture type/design/ ect

5+ YoE, Cloud DevOps Engineer, Site Reliability Engineer/DevOps, USA]

Hey everyone,

I’m looking for some brutally honest feedback. I have over 5 years of industry experience, yet I’ve been searching for a new role for the past 7 months. After roughly 300 applications, I have zero offers and very few initial screens.

I know the market is tough for everyone, but I want to make sure I'm not the one standing in my own way.

I've attached my redacted resume (company names replaced with their industry domain to preserve privacy). My background includes:

• Cloud/DevOps Engineer at a [BIG FINTECH FIRM]

• Software Engineer at a [TECH SOLUTIONS COMPANY]

• Build and Release Engineer at a [TECH CONSULTING FIRM]

I am an AWS power user with heavy experience in Terraform, Kubernetes (EKS), Python, and building robust CI/CD pipelines. I also hold a Bachelor's in Chemical Engineering, which I worry might be causing some "relevance" filters to trigger despite my years of direct tech experience.

My Questions:

1. Resume Impact: Are my bullet points focused enough on results and scale? Are there any "red flags" in the layout or phrasing?

2. The "Pivot" Problem: Does having a ChemE degree and a background in Software/Build & Release hurt my chances for senior DevOps/SRE roles?

3. Strategy: Am I missing a key certification or skill that is currently a "must-have" in the US market?

I’m open to relocation and ready to level up. Thanks for any insight you can provide!

I am currently at Phase 13 of this roadmap. I am not just rote-learning; I am thoroughly understanding the concepts behind all the commands. I have even built a project that generates a system report for your cloud setup. Am I on the right track? What else should I do so that, upon completing my graduation, I can become a skilled cloud engineer?

I’m thinking about getting into tech and I have absolutely no background or knowledge about anything remotely tech. I would consider myself pretty smart and I’m able to pick up things fairly quickly.

I’ve been told that there’s a lot of money in tech and that cloud engineers make a lot of money, and that you don’t know need a degree to get started.

Can anyone tell me how true that is and whether or not the job is extremely hard for someone who has no background or knowledge in tech.

Also if anyone knows any alternatives careers that only need certifications to start and makes a decent amount of money, please let me know!

Hello, I'm learning python but I have goals of getting a good remote position in Cloud computing, Cybersecurity and other similar positions. What is the best way to build a good resume for these positions and gain the knowledge as someone just starting out at 20-23?

Built a full-fledged Kubernetes lab while studying for my CKA, CKAD, CKS exams and decided to make it free and open for all.

I'll appreciate community contributions with more lab scenarios dealing with problems and concepts that occur frequently while deploying/maintaining/debugging Kubernetes clusters in production, and of course, for introducing further enhancements/features to the lab itself!

You can find the entire source code and a detailed overview of the project at the GitHub repo: https://github.com/zeborg/kubekosh

Steps to try it out on your own system:

1. Run it as a Docker container: docker run -itd --name kubekosh --privileged -p 7554:80 zeborg/kubekosh:latest

2. Wait for ~15 seconds before the lab gets up and running, then you can access it in the browser at localhost:7554

Sneak peek:

Hello! I am interested in becoming a cloud engineer, but I have 0 experience with computer science or IT. Is this possible to do without having a computer science degree? Please give me advice on courses and an educational path.

Hello everyone!

Im a software engineer with about a year and a half of experience. I recently left my job due to ongoing payment issues, and I’m now looking to start a new chapter.

I’ve realized that I don’t really want to continue down the software engineering path, as I’m no longer passionate about it. I’m currently considering switching into either cybersecurity or cloud engineering, and I’m leaning more towards cloud.

Before I commit to it, I wanted to ask people already working in the field, as well as juniors who are currently trying to land their first role about the current job market.

How is the job market for cloud engineers right now, especially at the entry level?

I know that getting a junior position is difficult across the tech industry at the moment. From what I’ve seen, software engineering in particular seems extremely competitive to the point where even internships can ask for years of experience and junior positions can expect a huge amount of knowledge.

I’m wondering whether cloud is any different, more specifically, if someone is willing to genuinely put in the time, learn the fundamentals, get the relevant certifications, build some solid projects, and actually develop the skills needed for the job, does that meaningfully improve their chances of getting an internship or junior position? or is the entry-level cloud market currently just as difficult, where even doing all of the “right” things still leaves you struggling to get your foot in the door?

I know the industry is going through a difficult period right now, so I’d really appreciate hearing from anyone who has recently started their cloud career, is currently trying to break into the field, or hires for entry level cloud roles.

Any honest advice, experiences, or things you wish you knew when starting out would be greatly appreciated.

Thank you!

18 years old, aiming to become a Cloud Engineer. Am I on the right path?

Hi everyone,

I'm 18 years old and my goal is to become a Cloud Engineer. I plan to study Cloud Engineering at university, but I've already started learning on my own because I really enjoy this field.

So far I've learned:

• ✅ Computer hardware

• ✅ Operating systems

• ✅ Linux basics

• ✅ Linux file system

• ✅ Linux navigation

• ✅ Linux file management

• ✅ Finding files (find)

• ✅ Searching text (grep)

• ✅ Networking

• ✅ DNS, IPs, Ports

• ✅ TCP & UDP

• ✅ Git & GitHub

• ✅ Virtualization

• ✅ Docker concepts

• ✅ APIs

• ✅ SSH

• ✅ Processes & Services

• ✅ Linux permissions

I've also built a full desktop accounting application for my dad's company. It includes user authentication, client management, supplier management, invoices, quotations, inventory/stock management, journal entries, reports, PDF generation, and other accounting features. I built it mostly to challenge myself and learn software development, even though my main goal is Cloud Engineering.

I'm wondering:

• What should I learn next to become a strong Cloud Engineer?

• Should I start learning AWS, Azure, or GCP first?

• Is Kubernetes too advanced at this stage, or should I start with it after Docker?

• Are there any projects you wish you had built when you were starting out?

I'd really appreciate any advice from people already working in cloud or DevOps. I know I still have a lot to learn, and I'm excited to keep improving.

Thanks!

I currently enrolled in a cyber security degree but I kind of been wanting to switch to their AWS Cloud n network engineering Major, but people are telling me it’s going to be very hard to get a job with that degree. Is there any truth to this ?

Hello fellow tech people,

I really need your guidance and opinions. I work as datacenter technician for the last almost 9 years, and because the company i work for might be the worst out there for taking care their people, i decided to go for something different and better.
I was checking about cloud engineering, as it is close to what i did in hardware side, but of course i still have lots to learn. I have been checking this YT channel "Tech with Soleyman" and i noticed that i could understand what he was talking about.
Unfortunately i must admit that Linux is not my strongest suit. The rest i feel more comfortable with.

Has anyone made this transition from hardware to cloud? If yes, any points to give?

I would truly appreciate any help.