Day-0 | Course Overview & Syllabus | 30 Days Of GitLab DevOps

Hello team and welcome back to the channel. My name is Adita Jwal and we are starting a new advanced GitLab DevOps series on this channel. And I can actually guarantee you that once you complete all the 30 videos of this series, you will be able to master advanced level of GitLab very easily. And this course is not just about writing pipeline. It's about end to end GitLab because GitLab is the only platform where you can get all the features of any DevOps platform. For example, CI/CD already you are aware uh of project management already you are aware because you can push the projects. You are also going to get the Jira kind of board inside GitLab to manage your project. That means project management can also be done very easily. Plus there are specific agents for Kubernetes deployments. So I'll explain like what other features are available. But trust me this is the only platform which has end to-end features that you will be needing to build and deploy application plus manage it properly. Right? That's why we are uh starting this series so we can make sure that this series will help you understand advanced level of GitLab very easily. But again you have to make sure you should be dedicated. It should not be like that you watch day zero and day one video then you are like now I will watch later. As soon as videos are uploaded make sure that you complete each day video on the same day. For example, if day one is added today, you need to make sure you are implementing it because we'll be focusing on making the videos practically because you know theoretical is fine but making things practically helps you understand in much better way and that's what we are trying to focus on. Now let me walk you through in detail through this syllabus what exactly we'll be covering in coming 30 days. Again guys make sure that uh you are watching this video properly making short notes also even though I will be providing my own notes inside the discord server but yeah I would highly recommend that make sure you watch your you make your own short notes as well. Now let me quickly walk you through the syllabus that we'll be covering.

So Tim now let us understand like why exactly we are preferring to choose GitLab for this video series and not GitHub actions. Okay. So let me explain you with respect to a proper table. So we can compare GitHub and GitLab properly. First of all in simple words if I have to tell you like why exactly I'm choosing GitLab for this video series is because like GitLab works like all in one platform that has everything that you require for performing a DevOps task. That means if you have a project you can ma perform the project management you can perform the ticketing task building CI/CD pipelines you can integrate built-in uh security uh scanning things and you can deploy properly you can perform monitoring also right but let us compare this one by one in proper format first talking about philosophy so GitLab at this point it's a single integrated deos platform as I told allin-one everything that you require will be there image registry package management everything will be built in present GitHub it's mostly ecosystem based that means we can integrate as per the requirement then talking about planning so you know when you are working with a DevOps project you have to make sure that all the work is tracked all the work progress is tracked that is how it is done in companies they use a platform known as Jira where they can create ticketing they can create different kind of tickets will be assigned to different developers and devops engineers so that all those uh employees they can mention their task and progress on it. So this is how like uh work progress is tracked that can be done using a built-in feature of GitLab which is which provides your issues boards and road maps in GitHub projects we don't have that GitHub projects is a very basic version of project management right source code this is going to be same in both of them cicd in GitHub we have GitHub actions pre-built in GitLab you simply have to start writing YAML file and that is all from security point of view in GitHub actions We have to integrate external tools. We have to install them and then we have to integrate them. But when it comes to GitLab, you are having a built-in feature for SAS scanning, dash scanning and dependency scanning. And that is one of the best part. You don't have to separately set up different kind of tools to integrate. Right. Container registry in GitLab. You'll be container registry where we are going to store our Docker images. For GitLab, it is already built in per project. for uh GitHub it is available but it's a separate service that you have to integrate artifacts and package management. So inside GitLab this is also built-in present in GitHub it is present as GitHub packages but it is a separate service deployment. So in GitLab you get Kubernetes agents directly connecting to Kubernetes for deployments plus autodevOps is there. This is something that we are going to understand in deep when we are once we are writing our pipeline in GitHub. You can integrate our god and terapform as a uh like uh separate integrations you can do for monitoring. So in GitHub actions you have to integrate external tools like graphfana data do but when we talk about uh gitlab so prometheus integration is present even though it is basic but it's a default integration that is already present separate integrations we can do configuration inside gitlab as we discussed it will be a single gitlab ci file inside github we can have multiple tools and configurations setup effort since gitlab is already having everything pre-built So setup effort will be very low but on uh GitHub actions it will be uh higher as compared to uh GitLab because there lot of integrations we have to do manually. Talking about flexibility here it's moderate and here in GitHub actions it is very high. I'll tell you one very important factor with respect to GitHub actions. So you know GitHub action should be preferred when you want to do lot of integrations. You want to create everything as per you your own requirement because you can do it manually inside GitLab. We actually have everything already created. We just need to start using it. Okay. One thing you should know at this point most organizations prefer GitLab. Why? Because you know first it reduces effort. It reduces cost also because everything will be pre-built. Everything is already created. You just need to start using it. So that will be there. And so at this point G gitlab is highly preferred in organizations and enterprise level task. Startups are flexible architectures they are still using GitHub because why? Because in startups there are lot of contig uh lot of like uh integrations needs to be done lot of changes needs to be done. So GitHub is quite good for that part. But yeah organizations usually prefer GitLab. So this is like why I'm choosing GitLab over GitHub. But now let us understand the actual syllabus that we'll be covering over 30 days of this course

course student. Now let us understand the syllabus in detail. What exactly we'll be learning properly. Right. First of all there will be around 30 videos the practical one including the day zero there will be 31 total videos. There will be total four weeks in which we are going to complete the course and on daily basis this videos will be uploaded one by one. Okay. And finally there will be one capstone project. As most of you already know capstone project is something where we integrate everything that we have learned. So that will be one project. Now let me explain you quickly how exactly you have to follow the course. Okay. Firstly you'll be explained like why we are covering this topic. You have to follow the video to understand the deep dive points of whatever topic we are covering. You need to make sure that you are actually building whatever we are teaching in the video. You have to make sure that you are implemented on the same day. Do not delay it that we'll do it tomorrow or the day after tomorrow. No, do it on the same day. And then [snorts] you have to update us as well. Since I have told you that inside Discord server, we are going to share all the documents, you have to update us there. If you face any issue, you have to let us know. Also, if you implement successfully, make sure to share it on LinkedIn for everyone else also to see. So Tim before we move ahead one very important thing that I need to tell you that just be consistent with the video series that is ongoing and I want that every one of you make sure that you are implementing uh the whatever task that is being given in on each day video and at the end of the series there will be one capstone project. So I want that everyone should be consistent making sure that everyone is implementing all the tasks given in each of the video including the capstone project posting it on LinkedIn and sharing it in our discord server for us to review. So once everyone is doing that and so uh top three people who will be doing this uh we'll be given a surprise gift right so yeah make sure to be consistent and make sure to uh implement everything that we are sharing. So once you complete the video make sure to update me over discord. Yes sad I have completed day one task. I have completed it. Uh I have completed watching the video and then you need to make sure or this will be your assignment that you need to actually implement it right you need to make sure that you are posting it on LinkedIn. Now question is why Adita we should be posting on LinkedIn because it's not just a post on LinkedIn. It will be it basically like you're creating a proof of your work right so that recruiters can actually see recruiters can see what you exactly you have done it will be like a your own like uh you can say live uh resume for you okay because any recruiter who's going through your profile if he sees that this is what this guy is learning so there is a chance that you can get at least opportunity for jobs And this is also going to help you stand out from others. For example, for people who are just uh who are just applying and not giving any kind of proof because in réumé adding things is fine but there should be some kind of proof available. Most people will add the GitHub uh repositories in rum but there is not it's not possible that every time recruiter will go through your repository completely. Right? So this is going to be really useful if you're posting it on LinkedIn and try to make sure that you are actually tagging me also. Why I'm saying that because uh once I because I can help you get more reach also because once I comment uh from my profile so it will be sh your post will be shown to my uh followers also and there are many recruiters in my uh connections. So I hope that is going to help you eventually right. So make sure this will be your assignment that I want that everyone should be completing it on the same day you're watching the video. Right now let's talk about in 30 days or in four weeks in 31 videos what exactly and how exactly we are going to cover. Okay. So let's talk about week one. Okay. Now in week one we are going to get started with platform foundation. Here directly we are not going to create the CI/CD pipeline. Right? We need to understand every single aspect of the pipeline right. So in week one we are going to understand about projects groups MRS code review container registry platform mastery what things we should be knowing before we create any pipeline right so in order to understand in detail we can understand we can go here in week one. So week one first we are going to get started with gitlab overview architecture of it rails gitlay radius sidekick portgress sql why each component exist we are going to understand then you are going to understand about code review and collaborations this parts uh projects groups and subgroups this is one of the most important part because when you set up your pro repository you need to understand where exactly it's going to set up right so you need to understand the hierarchy that is going to be available in between these components, right? Visibility labels and fork workflow, then issues, ports and agile planning. Basically, as I told you that there is a ticketing tool kind of option available inside GitLab. So, you need to understand about how to manage that, how to manage your project via that option. So, those things will be in that. Then we are going to understand about Git workflow and protected branches. A very important concept in from organization point of view, right? We are going to understand git flow versus trunk based, right? and branch protection rules. Then container registry and package registry which I told you that these are some services that are present inbuilt in each project. Then module request deep dive that will be our week one agenda. Right talking about week two. So in week two we are going to start with the CI/CD architecture and we are going to create a basic first pipeline. As I told you at the end of the video like at the end of the last video there we'll be doing a capstone project but we need to start with basics. So we are going to get started with uh basic pipeline we are going to understand executor types CI lend tool coordinator model these things. Then we are going to understand about runners how we can install and register and then configure VM as a runner. How we can utilize a free runner. Both the scenarios we are going to cover. Then we are going to understand about stages DAG and needs. How exactly? Because these things are required when you when it comes to write the proper end to end pipeline right then we are going to understand variables secrets and masking what exactly they are how to integrate it within our pipeline. Then comes the part artifacts and caching. So we are going to understand about how exactly we are going to be utilizing it in our pipeline. Then rules workflow and conditional pipeline. This is also something that I have including so that you can understand different scenarios of pipeline. If you want to write a condition based pipeline, how we can do that? Then debugging. Once you have understood how to write a basic pipeline indicating all these scenarios, then you should know how to debug a pipeline and how to optimize it. Optimize means how we can make the pipeline better, it faster, right? Then again in week two, these are the topics that we'll be covering in detail. comes the part week three where we are going to get started with docker security and cubernetes right so SAS and secret detection we'll be doing this is from sec secret point of view SAS tools we are going to use perform uh static application security testing and secret dete detection from the repository we are going to do that docker images we are going to understand uh DND and cano is something that most people might not know is something using which you can build your docker images inside the container itself inside the pod itself right so then separately we don't have to run the command like key docker build so it saves a lot of time then container scanning we are going to understand using trivia secret management with vault how we can manage secrets because we don't want to expose any kind of secrets that we use in our organization then how exactly we can perform deployment to kubernetes we can use cubectl helm in CI cube config all those things and role rollout status also we are going to use So all those things we'll be covering here. Then GitLab Kubernetes agent K this is a very important concept that most people do not study. So we are going to understand that as well how we can integrate GitHubs DAT with OSJ. DAST is something that like dynamic application security testing that is generally done after you have deployed your application so that you can make sure that once application is deployed there is no kind of like vulnerability available on the running application. So we can find out those things using OSPF which is a task tool. Then we are going to understand about environments approval and production. Basically it's not like we'll be deploying to only one environment. We'll be deploying the project to multiple environment. Lower uh we'll be deploying to lower environment. We'll be deploying to upper environment like prod. So those things also we are going to see. So these are the things that we are going to cover inside uh week three which is going to be security docker and kubernetes. Talking about week four here we are going to get started with advanc admin and hardening. Okay we are going to understand how we can perform review application review and dynamic environments management. How we can perform multiro and parent child pipelines. How we can create so that a parent pipeline can trigger a child once dry pipelines we are going to understand extends and include how exactly right then blue green and canary deployments we are going to perform deployment using blue green and canary both of them so we can understand different scenarios we'll be understanding about dora metrics and slack notifications once pipeline is completed how exactly we are going to get notified then gitlab administration it's a management kind of thing but yeah again it requires lot of technical tasks so that we are going to See then arbback and runner security hardening whatever VM you are going to add as a runner we have to perform the hardening of that as well right so these things will be there and you know final project will be there we are going to write the end toend pipeline deployment of the pipeline properly deploying to like lower environment deploy to upper environment then uh getting notified and then monitoring as well all these things will be there okay and our code will be completely reusable okay So that in that format we are going to write it. So let's be honest and let us understand what are the prerequisite for this course. So that you should be clear key if you are eligible for this or not. Okay. First of all it's course this course is uh again for all kind of people. This is for freshers. This is for people who are in uh already DevOps engineer. People who are on senior level people who are SR engineer because in each domain in on each level of your work this is going to be really useful talking about what are the prerequisite. So there should be some git basic knowledge you should be having. For example, you should be knowing how to perform g push uh how to create branches. So those basic things you should be knowing. Then some Linux commands because Linux is base of everything. So Linux command definitely you should be knowing how to run, where to run and how to connect to VMs. Those things should be there. Docker basics you should know how to run basic Docker commands, how to set up Docker, what exactly is Docker, those things also you should know. Then basic Kubernetes knowledge also should be having for example information about pod deployment those things should be there. I'm not talking about service and deep dive but basic knowledge of Kubernetes resources like pod should be there. Okay. And one gitlab. com free account you should be having. So if you are having these many things and you actually want to learn you really want to learn things in a very deep dive way then this course is for you. And again 100% free. this course is going to be 100% free forever. Okay. So yeah that those these are the things that we'll be covering in our course. So make sure to not meet miss any of the single videos and make sure to implement on the same day you are watching the video. Right. And yeah one more thing as I discussed that there will be assignments you need to make sure once you have completed you are updating me in discord server. If you face any issue you update me. Same thing on the discord server. If completed with the implementation make sure to put it on LinkedIn. you can tag me uh so I can also help you with the reach. Okay, so yeah, that's all and now let's get started with day one of the video.