DevOps Roadmap for beginners

Summary

In this video, Atheish provides a comprehensive roadmap for becoming a DevOps engineer. He explains that DevOps is about moving code from local development to production while ensuring its availability. The guide covers necessary skills, including basic Linux proficiency, Git, YAML, cloud services like AWS, Docker, Kubernetes, and tools like Terraform and Ansible. Atheish emphasizes hands-on experience and cloud environment practice, addressing concerns about job prospects for freshers in DevOps and offering advice on how to stand out in interviews by building real projects.

Takeaways

• 😀 DevOps engineers are responsible for moving code from localhost to production and ensuring it is always available.
• 🔧 DevOps does not require extensive programming knowledge, but understanding code basics is essential.
• 🖥️ Mastering Linux is critical for DevOps engineers, and spending at least two months learning it is recommended.
• 💾 Git and YAML are crucial tools for DevOps, and spending time mastering them will make tasks easier.
• ☁️ Becoming comfortable with cloud environments, especially AWS, is key to success in DevOps roles.
• 🐳 Understanding Docker and Kubernetes helps containerize applications and maintain cloud independence.
• 🏗️ Infrastructure as code is an important concept in DevOps, and tools like Terraform and Pulumi should be learned.
• 📊 Avoid falling into 'tool hell'—focus on mastering the key tools necessary for daily DevOps tasks.
• 🔍 There are fewer jobs for freshers in DevOps, but creating real-world projects and showcasing them on GitHub helps demonstrate experience.
• 📈 Certifications, such as AWS certifications, can add value to a resume and provide an advantage in job interviews.

Q & A

What is the primary role of a DevOps engineer according to the video?

The primary role of a DevOps engineer is to move code from the local environment to production and ensure it is always available to the client. This includes tasks like maintenance, updates, and continuous integration.

Is programming knowledge essential to becoming a DevOps engineer?

No, extensive programming knowledge is not required. DevOps engineers should be able to read and understand code, but they do not need to write complex business logic. Their main focus is on the tools and processes to move and maintain code.

Why is Linux knowledge considered crucial for a DevOps engineer?

Linux is foundational for DevOps because most cloud environments use Linux-based servers. Understanding Linux commands, networking, disk management, and namespaces is essential to manage infrastructure efficiently.

How important is familiarity with Git for a DevOps engineer?

Familiarity with Git is very important because DevOps engineers frequently interact with code repositories. Understanding Git concepts and being comfortable with version control will make a DevOps engineer's life easier.

What is YAML, and why is it important in DevOps?

YAML is a simple instruction set language used to configure infrastructure. DevOps engineers use it to describe the environment setup, such as defining the RAM, machines, and databases needed for deployment.

Which cloud platforms are most relevant for DevOps, and which one does the speaker prefer?

The most relevant cloud platforms for DevOps are AWS, Azure, and Google Cloud Platform (GCP). The speaker prefers AWS because it offers many services, is in high demand, and is used by many startups.

What role do Docker and Kubernetes play in the DevOps process?

Docker allows applications to be containerized and run consistently across different environments, while Kubernetes manages and orchestrates these containers, ensuring they are always running and scaling as needed.

What is infrastructure as code (IAC), and why is it important for DevOps engineers?

Infrastructure as Code (IAC) allows DevOps engineers to define and manage infrastructure using code instead of manual processes. Tools like Terraform or Pulumi help automate the setup and management of infrastructure, making it faster and more efficient.

What advice does the speaker give to aspiring DevOps engineers regarding tool selection?

The speaker advises not to fall into 'tool hell,' where engineers try to learn every tool available. Instead, focus on mastering a few core tools and understanding the day-to-day operations of a DevOps engineer.

How can a fresher stand out when applying for DevOps roles?

A fresher can stand out by gaining hands-on experience, such as using AWS, creating GitHub repositories with YAML configurations, and showcasing their work in projects. This demonstrates real-world knowledge, even without formal job experience.

Outlines

00:00

🎤 Bass in Morning Recordings and Freshers in DevOps

The speaker humorously notes how recording videos in the morning deepens their voice, comparing it to Samuel Jackson. They then pose a question to viewers about the common belief that freshers cannot secure jobs in DevOps. While acknowledging this as a widespread claim, they point out that people still manage to land DevOps roles and promise to return to this topic later in the video.

05:00

🚀 Introduction to the DevOps Engineer Roadmap

The speaker begins the roadmap to becoming a DevOps engineer, stressing that this guide will be precise and practical. While DevOps is often described as a 'mindset' or 'cultural shift,' the speaker simplifies the role: moving code from a developer’s local environment to production, ensuring uptime and functionality for clients. This involves continuous integration and maintenance but centers around deploying and managing code across different environments.

10:02

💻 Programming Skills and Application Management in DevOps

The speaker explains that DevOps engineers do not need to focus heavily on programming, though some knowledge is helpful. They emphasize that understanding how to read and deploy code is more important than writing business logic. Regardless of application complexity, DevOps engineers approach tasks like deploying code, managing servers, and setting up databases similarly. While programming skills are an advantage, the speaker encourages learners to focus on tools and infrastructure rather than coding itself.

🐧 Mastering Linux for DevOps

The first major step in becoming a DevOps engineer is to become proficient in Linux, with a recommended two months of dedicated learning. The speaker highlights the importance of Linux knowledge across different cloud platforms (AWS, GCP, Azure) and encourages installing Linux as the main operating system for faster learning. The Linux foundation is essential, covering topics like disk management, networking, and namespaces, which are crucial for understanding containers like Docker.

🔧 GIT, YAML, and Their Role in DevOps

Once Linux proficiency is achieved, the next step is mastering Git, an essential version control tool used frequently by DevOps engineers. The speaker advises spending time on Git concepts, followed by learning YAML for infrastructure configuration. YAML is important for defining cloud infrastructure without programming and is a key language in DevOps. Understanding these tools will simplify the process of deploying and managing infrastructure.

☁️ Cloud Skills and AWS Focus

After mastering Git and YAML, the speaker recommends focusing on cloud platforms, specifically AWS. They explain that AWS offers the most widely-used services, making it a valuable skill in the job market. The speaker advises real-world practice by spinning up servers in AWS, overcoming the fear of running up high bills, and learning cloud scaling (both horizontal and vertical). AWS certifications can also add credibility and boost a DevOps candidate’s resume.

📦 Docker, Kubernetes, and Cloud Independence

Next, the speaker introduces Docker and Kubernetes, explaining how Docker containers applications for deployment and Kubernetes manages containers across servers. Kubernetes is especially valued for making deployments cloud-independent, allowing the same configurations to be used across AWS, GCP, and other cloud providers. Mastering these tools positions a learner well into the DevOps journey, preparing them to manage scalable, reliable infrastructures.

🛠 Advanced Tools: Terraform, Ansible, CI/CD Pipelines

With a strong foundation, the speaker suggests learning advanced tools such as Terraform, Ansible, GitHub Actions, and Argo CD for automating infrastructure. These tools allow DevOps engineers to define infrastructure as code and automate deployments and scaling. While these tools are essential, the speaker cautions against falling into 'tool hell,' focusing instead on understanding daily DevOps workflows, such as containerizing apps and ensuring they are scalable.

🔍 Avoiding Tool Hell and Simulating Real DevOps Workflows

The speaker warns about the trap of learning too many tools without understanding their practical applications. They stress that a good DevOps engineer focuses on understanding real workflows, like making applications scalable and monitoring them, rather than mastering every possible tool. Success in DevOps means being efficient and unnoticed, as seamless operations suggest nothing is going wrong. The speaker emphasizes practical experience over tool collection.

🛠 Gaining Experience and Proving Skills in DevOps

Addressing the challenge of landing a job as a fresher in DevOps, the speaker advises taking proactive steps to gain experience through self-directed projects. By sharing code on platforms like GitHub and showcasing work with YAML and cloud infrastructure, candidates can demonstrate skills to potential employers. The speaker promises to provide use cases and examples in future videos, encouraging learners to build a portfolio of hands-on experience.

📈 Final Thoughts and Encouragement for DevOps Learners

The speaker concludes by reaffirming the goal of the video: providing a clear and precise roadmap to becoming a DevOps engineer. They invite viewers to engage through comments or reach out on social media with questions. By following this roadmap and gaining practical experience, aspiring DevOps engineers can confidently approach job opportunities. The speaker also invites feedback and encourages subscriptions for more in-depth guides in the future.

Keywords

💡DevOps

DevOps refers to a set of practices that combines software development (Dev) and IT operations (Ops) to shorten the systems development life cycle. In the video, it is framed as a mindset and cultural approach but with a focus on practical skills. The speaker defines DevOps as the process of moving code from local environments to production, ensuring it's always available to clients.

💡Linux

Linux is a popular open-source operating system that's essential for DevOps engineers. The speaker emphasizes the importance of mastering Linux as a prerequisite for a career in DevOps, suggesting at least two months of focused learning. Understanding basic commands, networking, and disk management are key elements that make Linux a core skill in the field.

💡Cloud

Cloud computing involves the delivery of various services, such as servers and databases, over the internet. The speaker discusses how DevOps engineers must be comfortable working in cloud environments like AWS, GCP, or Azure. Familiarity with cloud services allows engineers to scale applications and infrastructure efficiently.

💡Docker

Docker is a platform that enables DevOps engineers to containerize applications, meaning packaging code and its dependencies into a 'container' that can run consistently across different environments. In the video, Docker is positioned as essential for deploying and managing applications across multiple servers.

💡Kubernetes

Kubernetes is an open-source platform used for automating the deployment, scaling, and management of containerized applications. The speaker explains that Kubernetes helps DevOps engineers keep applications running smoothly by distributing workloads across servers, making it a vital tool in cloud-agnostic environments.

💡Git

Git is a version control system used to track changes in code and collaborate with other developers. The speaker stresses the importance of mastering Git for DevOps engineers, as they will often be dealing with repositories hosted on platforms like GitHub or GitLab. Knowledge of Git simplifies code management and deployment.

💡CI/CD

Continuous Integration and Continuous Deployment (CI/CD) are practices that automate the process of testing and deploying code changes. The speaker mentions that maintaining smooth updates and integration of code is a key responsibility for DevOps engineers. Tools like CircleCI or GitHub Actions are commonly used to implement CI/CD pipelines.

💡YAML

YAML (Yet Another Markup Language) is a human-readable data serialization format used for writing configuration files. In the video, the speaker suggests spending a few days learning YAML, as it plays a crucial role in defining infrastructure as code. YAML files can specify how servers and databases should be configured and deployed.

💡Infrastructure as Code (IaC)

Infrastructure as Code (IaC) is the process of managing and provisioning computing infrastructure through machine-readable configuration files, rather than manual hardware configurations. The speaker advises learning tools like Terraform and Pulumi, which are used to write IaC scripts that automate the creation and management of cloud infrastructure.

💡AWS

Amazon Web Services (AWS) is a comprehensive cloud computing platform offered by Amazon. The speaker highlights AWS as a preferred cloud provider, especially for its wide range of services and industry demand. Learning AWS helps DevOps engineers deploy, manage, and scale applications, with certification boosting job prospects.

Highlights

Recording videos early in the morning adds too much bass, making the speaker sound like Samuel Jackson.

DevOps jobs for freshers are limited across industries like web and mobile development, but it is still possible to crack a job.

A DevOps engineer's main role is to move code from a local environment to production and ensure it’s always available to clients.

Programming is not a core requirement for DevOps, but having basic understanding of code is beneficial for troubleshooting.

Linux knowledge is crucial for DevOps engineers, and dedicating at least two months to mastering it is highly recommended.

YAML, a non-programming language for writing instructions for infrastructure, can be learned in about two days and is essential in DevOps.

Learning cloud platforms like AWS, Azure, or GCP is essential as these environments are core to DevOps work.

AWS is preferred for its broad service offerings, but the skills are transferrable to other cloud providers like Azure and GCP.

Docker and Kubernetes are important tools for containerization and orchestration in the DevOps world, and they make applications cloud-independent.

DevOps engineers should focus on understanding core tasks like scaling applications and managing infrastructure instead of learning every tool.

Infrastructure as Code tools, such as Terraform and Pulumi, are key to automating infrastructure setup and should be mastered.

Being unnoticed is the hallmark of a good DevOps engineer; if things are running smoothly, no one will ask about the DevOps team.

For freshers, gaining practical experience by working on personal projects and uploading them to GitHub can be key to landing a job.

Self-experience in DevOps can be demonstrated by working on projects like creating scalable applications or configuring cloud environments.

The video offers a precise, non-vague roadmap to becoming a DevOps engineer, focusing on key skill sets and practical guidance.

Transcripts

the moment I record a video early in the

morning it adds too much of bass I sound

like Samuel Jackson okay here's a quick

question for you let me know in the

comments section have you ever heard

that nobody is giving jobs to fresher in

the devops industry if that is true how

come anybody is ever cracking a job in

the devops industry and here's a fact on

top of this nobody likes to give a job

to fresher even for web development

mobile development or anything else as a

matter of fact I'll come back on to this

one and we'll talk in depth of this

later on in this video first let's go

ahead and get started with the road map

to become a devops engineer hey there

everyone atheish here back again with

another video and in this video I'll

give you a precise road map to become a

devops engineer so that if you're

learning on your own or maybe following

some other resources as well you can

actually find out that what I need to

learn and what order I need to learn

it's not a vague guide which includes

everything that is possibly there in the

devops but a precise roadmap that can

give you on some path I am very much

sure that you have heard about the term

devops and you are pretty much

interested in that and you have heard

things like devops is a mindset devops

is more like a cultural thing in your

company I agree to some extent but it's

not about the cultural activities that

somebody is hiring you for the devops

yes it's great to sound but the whole

idea and a shortcut hacky definition of

devops is people write code on the

localhost it's the devops engineers

responsibility to move that code into

the production and make sure it is

always available to the client that is

the gist of it and that's what the

devops engineer do in the day-to-day

life yes it includes a lot of things

about maintenance updates continuous

integration a lot of things but that's

the whole idea the journey is from The

Local Host to the production environment

now the first obvious question is what

should I know already in advance to

become a devops engineer do I need to

learn ton of programming the good thing

a lot of people love that is that devops

doesn't require you to have too much

understanding of programming you should

definitely be able to read the code and

get an overview what does this code look

like and what it's going to do what I

need to install but you don't need to

write business Logics that's the job of

developers not the devops for a devops

engineer any application that is a basic

to do which is adding a to-do's and

adding them into the database maybe

postgres MySQL or mongodb is exactly

same as some complex application which

is processing too much of data and then

putting it into the database yeah surely

there could be difference in how the

servers are what the configuration is

but for us it's devops engineer it's

exactly the same application we need to

move it on to the server spin up few

machines and put up a database behind it

surely if you have programming

experience you are going to thrive a lot

in the world of devops because you

understand the code a lot but it's not

really compulsory and you can totally

totally not focus on the programming

ball surely you cannot totally ignore it

but you can move your focus a lot more

on the tools and the skill sets that are

required to become devops engineers all

right now that the prerequisites are

complete let's go ahead and move on and

understand the journey to become a

devops engineer the step one to become a

devops engineer is to spend a lot of

time on Linux and at least I recommend

at two months a dedicated two months to

be on Linux no matter what cloud

infrastructure you are choosing to move

your production code maybe that's the

basic Linux servers or maybe that's AWS

gcp Azure one thing which is common in

all the devops engineer skill set is

Linux and the more you know about Linux

the better it is and understand the

basic commands of it how the graph works

and understand the basic networking of

it the Disk Management how it works how

the namespaces work in the Linux spoiler

alert namespaces are a great Concept in

Linux and somewhat inspired how the

containerization and Docker works so the

whole idea is the more you know your

Linux the more you're going to be

performing better as a devops engineer

and I would not hesitate to recommend

that if you are really serious becoming

a devops engineer don't hesitate to

install Linux onto your even Main

machine make sure to do take the backup

you will be crying a lot a little bit

probably a lot and it is not going to be

an easy Journey probably your videos are

not going to play probably your drivers

are not going to make sense but the

fast-paced way of learning in Linux is

simply to install it on their main

machine and cry out every day the

foundation of Linux is just Linux it

doesn't really matter too much so if you

are a fanboy of Ubuntu or maybe Centos

maybe pop OS whatever suits you just go

ahead and get friendly with the Linux

environment once you feel absolutely

comfortable with Linux then go ahead and

move on with the git now it doesn't

really matter if it is a git lab or

GitHub the git concepts are really

important you'll be dealing with them

quite a lot so having a comfortable life

with a git is going to make your life a

lot easier so spend some time on git

after that once you're done with that I

recommend you to spend some time or

probably two days with the yaml yes two

days are more than enough to learn and

understand yaml yaml is more of a like

an instructional set language it doesn't

include any program programming it's

just an instruction that eventually you

will be using as a devops engineer these

instructions are given to the computers

that hey I need an infrastructure maybe

which has this much of RAM and this much

of machines and I want to set up a

database all this you can write in the

instruction we'll talk about that later

on but yaml is one of the language which

I highly recommend that you master early

on in your devops journey alright you

have done this much great start as a

devops engineer now the life of a devops

engineer revolves around a lot of code

yes there are dedicated Cloud engineers

and the devops and yes people do

consider them as separate one but the

chances are high that you need to have

this knowledge as well now pick up your

favorite Cloud for me it's going to be

AWS but it's equally same for Azure and

gcp as well AWS offer a lot more

services and is a lot more in demand and

a lot of startups use them but the

demand for AWS and Azure are kind of

growing at the same time and the most

important part is the machines the

servers that you're spinning up are

gonna cost almost equally same on AWS

and Azure yes I know there's a

difference but the point of saying that

is you'll be spinning some servers it

doesn't really matter you are borrowing

these machines from Jeff Bezos or maybe

Sundar pichai you need to borrow them

with someone the more you are

comfortable with the cloud environment

the more you are making your life easier

now I personally prefer AWS on that

because you can actually easily complete

a few certification on AWS as well

during this journey and that will surely

add an added Advantage into your resume

as well as in your interview as well it

gives a confidence to the person who is

hiring that this guy knows his stuff he

has also proven that why some

certification in case you want to do

that otherwise having the knowledge

in-depth knowledge of the cloud and ins

and out how that works is really

essential and one thing I would like to

add here is that it's not about working

in a controlled environment the true

knowledge of cloud comes up when you

actually jump into the main Cloud yes

I'm pretty sure a lot of you might be

afraid of spinning up the servers may be

ramping up the bill that's okay AWS is

really friendly and even if you shoot up

an email that hey I was just learning

probably I accidentally shot up the

email and the bill you can actually go

ahead and reduce them down but the idea

is play in the real Waters and learn

there so don't be hesitant too much with

the AWS if you're following a proper

guide if you are having a good Mentor

who is teaching you well I'm sure that

you will be comfortable in not spinning

up the bill too much listen closely and

you won't be a hesitant there but again

here's my personal advice learn AWS in

the Real Environment will help you a lot

let's just say you have picked up AWS

and now you're quite comfortable with

spinning up machines and even horizontal

scaling vertical scaling you know about

what kind of storage is given to you

you're pretty much comfortable with AWS

what next then comes up two most

important Technologies which are used

these days quite a lot the docker and

the kubernetes docker is a way how you

containerize your application and put

that onto the servers and in order to

make sure that these servers and these

containers basically are always up and

running if some container goes bad and

goes down there is something which is

monitoring them and making sure that

these containers are available all the

time the load on one machine is not too

much you can kind of distribute your

load with different containers on

different machine that is where your

kubernetes comes into the picture yes I

agree the name kubernetes sounds

daunting but it makes you Cloud

independent you can spin up the same

servers and same configurations same

containers in AWS and gcp and you can

move on freely and that is why people

love kubernetes so much alright you have

done so much that means you are already

60 to 70 percent into the devops your

name and probably you are also ready to

apply for a lot of companies and yes it

doesn't make you a full grade Pro devops

engineer but I think you have gone a

great start so only this much of the

topic will make you a really good devops

engineer but obviously you are into the

roadmap you want to take one step

further now comes the Journey of

learning about the tools and the

terraform the tools like ansible

something like GitHub actions Argo CD or

maybe Circle CI these tools are not

going to take too much of the time

because you have spent good amount of

time in working up of your foundation

all of these uh probably each one is

going to take a week or probably 15 days

to get started not to master it but to

have enough knowledge that you can

present yourself that I know some stuff

about it after doing this much I would

personally recommend you to spend a lot

of time with infrastructure as a code

and there are a lot of tools for it

something like terraform maybe pulumi

yes there are more coming out every

single day but once you understand the

concept of how to write configuration in

a yaml file and then make it up and

running and you can spin up an entire

infrastructure for a company with just

some line of code not just basically

code instructional code yes yaml files

then you will understand the true power

of what infrastructure of infrastructure

as a code is one personal advice I would

like to give you at this point if you

have gone through with all those tools

that I have mentioned right now the tool

list never ends there could be

Prometheus there could be grafana and

there could be more monitoring tool that

will help a devops engineer to walk

through in the daily life but don't fall

into the tool hell yes just like we have

a tutorial hell we also have a tool hell

in the devops world learning unlimited

tools is not going to make you a better

devops engineer the better devops

engineer you're going to become when

you're going to actually understand that

what is the daily working of the devops

engineer and can I simulate that can I

go ahead and just make or take a dummy

application and can make it scalable

onto the cloud how can I monitor that

can I containerize that that is going to

make you a better devops engineer than

instead of just falling into the tools

hell remember the best devops engineer

is somebody who is not being noticed in

the company if you are getting noticed

every week in the company that means

something is going down devops is kind

of a role where nobody asks you where

you are even if everything is running

fine in the company so make sure you can

and that kind of devops engineer after

this comes up to the very first point

who is going to hire fresher in the

devops industry I agree that the jobs

for the freshers and devops Industry are

little bit scarce and it's not like too

much there are still enough of plethora

of jobs for junior devops engineer the

idea behind making yourself skilled and

making yourself in a friendly with the

project is to work and just again as I

say a lot of people comes from a very

containerized environment they haven't

learned or even logged in into AWS

environment these kinds of people are

considered as fresher just like in the

web development somebody comes up that

hey I have created my e-commerce

application and I have pushed this app

and my apps are there in the Android

store he's not fresher obviously he has

not worked in the company but he's not

fresher he knows what he's doing

similarly in the devops world you can

put some of the code on your GitHub and

can say that hey this is the code that I

have been using and this is the code

that I've been creating in the yaml file

to do this to do XYZ I'll definitely if

you request enough if in the comment

section I'll come up with some of the

use cases and I can give you some of the

examples that hey these are the things

that you can do in your devops journey

and can present them to your interviewer

that hey these are the work that I have

done this is known as taking experience

on your own and yes there are many ways

how you can do it if enough people

request in the comment section I'll give

you a list of four to five such of

self-experience that you can take as a

devops engineer this guide was designed

so that you don't get bogged down and

you don't get confused as a devops

engineer you get a clear precise path of

how to become a devops engineer and what

all the tool set and skill sets that you

need to learn I hope you have enjoyed

that in case you have enjoyed that check

out links in the comments section first

pin comment of course and make sure you

comment down that how do you like the

video if you like more such video which

are not just the superficial videos the

in-depth guide of how we use it every

single day how we teach stuff and how do

we write code and devop stuff make sure

you hit that subscribe button I would be

really really happy with that in case

not that's also it's fine then you can

hang it on on the channel anyways if you

have any doubt at all go ahead and reach

me out on my Instagram I'm super active

there or put a question on my LinkedIn

inbox I would be happy to answer any of

the question that you have that's it for

this video hit that subscribe and let's

catch up in the next video