The DevOps Routine That Made Me Rich (Not What You Think)

Hey, what's up? In this video, I'm going Hey, what's up? In this video, I'm going to share what a day in the life of an to share what a day in the life of an to share what a day in the life of an actual DevOps engineer looks like. Now, actual DevOps engineer looks like. Now, actual DevOps engineer looks like. Now, every week, dozens of people apply for every week, dozens of people apply for every week, dozens of people apply for my mentorship, but when I talk to them, my mentorship, but when I talk to them, my mentorship, but when I talk to them, many of them actually have no idea what many of them actually have no idea what many of them actually have no idea what [music] DevOps engineers actually do. [music] DevOps engineers actually do. [music] DevOps engineers actually do. So, in this video, I'm going to share So, in this video, I'm going to share So, in this video, I'm going to share what a day in the life looks like based what a day in the life looks like based what a day in the life looks like based on the jobs that I've had myself. Now, on the jobs that I've had myself. Now, on the jobs that I've had myself. Now, when I say day in the life of DevOps when I say day in the life of DevOps when I say day in the life of DevOps engineer, that is already a little bit engineer, that is already a little bit engineer, that is already a little bit murky because the title of DevOps murky because the title of DevOps murky because the title of DevOps engineer is wildly different from engineer is wildly different from engineer is wildly different from country to country and from organization country to country and from organization country to country and from organization to organization. So, when I say DevOps to organization. So, when I say DevOps to organization. So, when I say DevOps engineer, like take that with a grain of engineer, like take that with a grain of engineer, like take that with a grain of salt because actually what you will see salt because actually what you will see salt because actually what you will see is that that my first job was more like is that that my first job was more like is that that my first job was more like a Linux sysadmin, my second job was more a Linux sysadmin, my second job was more a Linux sysadmin, my second job was more like an enterprise cloud operations like an enterprise cloud operations like an enterprise cloud operations engineer, and my third job was more like engineer, and my third job was more like engineer, and my third job was more like a platform engineer. And these are just a platform engineer. And these are just a platform engineer. And these are just some of the jobs I've had, not all of some of the jobs I've had, not all of some of the jobs I've had, not all of them, but from every job, my official them, but from every job, my official them, but from every job, my official title was DevOps engineer, but the title was DevOps engineer, but the title was DevOps engineer, but the actual interpretation of that varied actual interpretation of that varied actual interpretation of that varied from job to job. So, rather than from job to job. So, rather than from job to job. So, rather than focusing on the title, I'm just going to focusing on the title, I'm just going to focusing on the title, I'm just going to focus on what I actually did. So, let's focus on what I actually did. So, let's focus on what I actually did. So, let's jump in. But before we jump in, my team jump in. But before we jump in, my team jump in. But before we jump in, my team shared something with me that I want to shared something with me that I want to shared something with me that I want to share with you as well, which is that share with you as well, which is that share with you as well, which is that 78% of you guys who are watching my 78% of you guys who are watching my 78% of you guys who are watching my channel are not subscribed yet. And we channel are not subscribed yet. And we channel are not subscribed yet. And we can see that there are plenty of people can see that there are plenty of people can see that there are plenty of people who watch my videos every single week who watch my videos every single week who watch my videos every single week who have not subscribed. So, if you are who have not subscribed. So, if you are who have not subscribed. So, if you are watching my videos, I just want to ask watching my videos, I just want to ask watching my videos, I just want to ask you, please click the subscribe button you, please click the subscribe button you, please click the subscribe button down below. It is a completely free way down below. It is a completely free way down below. It is a completely free way to support this channel. And as you can

to support this channel. And as you can to support this channel. And as you can see, we are very close to reaching a see, we are very close to reaching a see, we are very close to reaching a very important milestone for our very important milestone for our very important milestone for our channel. I never thought that we could channel. I never thought that we could channel. I never thought that we could make it, but when I started out making make it, but when I started out making make it, but when I started out making these niche DevOps videos about Vim these niche DevOps videos about Vim these niche DevOps videos about Vim almost 5 years ago now, but we're almost 5 years ago now, but we're almost 5 years ago now, but we're getting really close. So, if you ever getting really close. So, if you ever getting really close. So, if you ever got any value out of my videos over got any value out of my videos over got any value out of my videos over these years, please just take the time these years, please just take the time these years, please just take the time and click it takes 1 second, click the and click it takes 1 second, click the and click it takes 1 second, click the subscribe button down below. It truly subscribe button down below. It truly subscribe button down below. It truly helps me. It really supports the helps me. It really supports the helps me. It really supports the channel. It helps us grow and reach more channel. It helps us grow and reach more channel. It helps us grow and reach more people like you who get value out of my people like you who get value out of my people like you who get value out of my videos. Thank you so much. Thank you for videos. Thank you so much. Thank you for videos. Thank you so much. Thank you for being on the journey with me, and now being on the journey with me, and now being on the journey with me, and now let's jump in. Now, across these three let's jump in. Now, across these three let's jump in. Now, across these three jobs that I'm going to share with you, jobs that I'm going to share with you, jobs that I'm going to share with you, there were a few things that were the there were a few things that were the there were a few things that were the same with every job. The first thing same with every job. The first thing same with every job. The first thing there is that you usually log in in the there is that you usually log in in the there is that you usually log in in the morning almost always from home, and you morning almost always from home, and you morning almost always from home, and you have what's called a stand-up. This is a have what's called a stand-up. This is a have what's called a stand-up. This is a short meeting, maybe 15, sometimes 30 short meeting, maybe 15, sometimes 30 short meeting, maybe 15, sometimes 30 minutes, where everyone logs in, and minutes, where everyone logs in, and minutes, where everyone logs in, and then they'll share what they did then they'll share what they did then they'll share what they did yesterday, what they're going to be yesterday, what they're going to be yesterday, what they're going to be doing today, and whether they have any doing today, and whether they have any doing today, and whether they have any blockers. This is something that I've blockers. This is something that I've blockers. This is something that I've had in every single job that I've worked had in every single job that I've worked had in every single job that I've worked so far. And then, depending on the so far. And then, depending on the so far. And then, depending on the company, there's usually a few recurring company, there's usually a few recurring company, there's usually a few recurring meetings that you have every week or meetings that you have every week or meetings that you have every week or every other week. Most companies are every other week. Most companies are every other week. Most companies are using the Agile methodology also for using the Agile methodology also for using the Agile methodology also for DevOps teams, so you will have things DevOps teams, so you will have things DevOps teams, so you will have things like backlog refinement, sprint like backlog refinement, sprint like backlog refinement, sprint planning, and these kinds of typical planning, and these kinds of typical planning, and these kinds of typical Agile meetings. And then, the second Agile meetings. And then, the second Agile meetings. And then, the second thing that was the same across all of thing that was the same across all of thing that was the same across all of these jobs is that the the day or the

these jobs is that the the day or the these jobs is that the the day or the week or the month even is usually split week or the month even is usually split week or the month even is usually split between two types of work. The first between two types of work. The first between two types of work. The first type being reactive, so you're type being reactive, so you're type being reactive, so you're responding to incidents or responding to responding to incidents or responding to responding to incidents or responding to support tickets and things like that. support tickets and things like that. support tickets and things like that. And the second thing being proactive And the second thing being proactive And the second thing being proactive work, where you are actively building work, where you are actively building work, where you are actively building new systems, you are making changes, you new systems, you are making changes, you new systems, you are making changes, you are implementing things, performing are implementing things, performing are implementing things, performing maintenance, that kind of thing. So, maintenance, that kind of thing. So, maintenance, that kind of thing. So, it's proactive and reactive work. And it's proactive and reactive work. And it's proactive and reactive work. And many of these jobs that I've had, many of these jobs that I've had, many of these jobs that I've had, actually every day consisted of these actually every day consisted of these actually every day consisted of these two types of work. So, it's actually two types of work. So, it's actually two types of work. So, it's actually quite a varied work day that you usually quite a varied work day that you usually quite a varied work day that you usually have as a DevOps engineer. So, there is have as a DevOps engineer. So, there is have as a DevOps engineer. So, there is this balance between firefighting and this balance between firefighting and this balance between firefighting and focused work where you are just alone focused work where you are just alone focused work where you are just alone and working on some cool project. Now, and working on some cool project. Now, and working on some cool project. Now, of course, this is going to be different of course, this is going to be different of course, this is going to be different from everyone. There are also going to from everyone. There are also going to from everyone. There are also going to be people writing angry comments in be people writing angry comments in be people writing angry comments in right now, "That's not what DevOps is." right now, "That's not what DevOps is." right now, "That's not what DevOps is." But this has just been my own experience But this has just been my own experience But this has just been my own experience in my own DevOps journey, and that is in my own DevOps journey, and that is in my own DevOps journey, and that is what I'm sharing here. So, those were what I'm sharing here. So, those were what I'm sharing here. So, those were the common patterns that I've seen the common patterns that I've seen the common patterns that I've seen across these jobs. So, let's just jump across these jobs. So, let's just jump across these jobs. So, let's just jump into the first job that I've had, which into the first job that I've had, which into the first job that I've had, which is my my my first junior DevOps job, is my my my first junior DevOps job, is my my my first junior DevOps job, which was at the Gemeente Amsterdam, the which was at the Gemeente Amsterdam, the which was at the Gemeente Amsterdam, the city of Amsterdam.

city of Amsterdam. city of Amsterdam. And this is a very large government And this is a very large government And this is a very large government organization where I joined the a DevOps organization where I joined the a DevOps organization where I joined the a DevOps team. Now, team. Now, team. Now, this this team, this this area was this this team, this this area was this this team, this this area was almost like a startup within this huge almost like a startup within this huge almost like a startup within this huge government organization. So, there was a government organization. So, there was a government organization. So, there was a lot of freedom in that sense. It was We lot of freedom in that sense. It was We lot of freedom in that sense. It was We weren't restricted by the usual IT weren't restricted by the usual IT weren't restricted by the usual IT regulations that the others had because regulations that the others had because regulations that the others had because we were not running extremely important we were not running extremely important we were not running extremely important applications in that sense. These were applications in that sense. These were applications in that sense. These were all data-driven applications. The one all data-driven applications. The one all data-driven applications. The one example was, for example, that there was example was, for example, that there was example was, for example, that there was an application that every morning would an application that every morning would an application that every morning would analyze analyze analyze in the city and the planned ship traffic in the city and the planned ship traffic in the city and the planned ship traffic based on the bridges and and all of the based on the bridges and and all of the based on the bridges and and all of the current traffic, it would calculate the current traffic, it would calculate the current traffic, it would calculate the most optimal garbage collection routes most optimal garbage collection routes most optimal garbage collection routes for the garbage trucks. Now, these for the garbage trucks. Now, these for the garbage trucks. Now, these operations, like the garbage collection, operations, like the garbage collection, operations, like the garbage collection, would not stop if they didn't have the would not stop if they didn't have the would not stop if they didn't have the optimal route, but it was still a pretty optimal route, but it was still a pretty optimal route, but it was still a pretty important thing. So, that's why we important thing. So, that's why we important thing. So, that's why we didn't have as strict of a regulation as didn't have as strict of a regulation as didn't have as strict of a regulation as other teams we had in the in the other teams we had in the in the other teams we had in the in the company, which meant that we could also company, which meant that we could also company, which meant that we could also take bigger risks, which was take bigger risks, which was take bigger risks, which was interesting. I was part of a DevOps team interesting. I was part of a DevOps team interesting. I was part of a DevOps team which supported about 20 developer which supported about 20 developer which supported about 20 developer teams. And going from this proactive and teams. And going from this proactive and teams. And going from this proactive and reactive, like the the the reactive work reactive, like the the the reactive work reactive, like the the the reactive work was something that we called the support was something that we called the support was something that we called the support shift. Now, this was organized in such a shift. Now, this was organized in such a shift. Now, this was organized in such a way where we had a Slack channel, and way where we had a Slack channel, and way where we had a Slack channel, and all of these developer teams were in

all of these developer teams were in all of these developer teams were in that Slack channel, and then whenever a that Slack channel, and then whenever a that Slack channel, and then whenever a team needed support or help with that, team needed support or help with that, team needed support or help with that, they would post a message in the Slack they would post a message in the Slack they would post a message in the Slack channel, and then your task was to channel, and then your task was to channel, and then your task was to you mark these messages, we call them you mark these messages, we call them you mark these messages, we call them tickets, you mark the message as with tickets, you mark the message as with tickets, you mark the message as with ticket with the eye emoji that someone ticket with the eye emoji that someone ticket with the eye emoji that someone was looking at it, and then it was your was looking at it, and then it was your was looking at it, and then it was your job to fix it. Now, this environment job to fix it. Now, this environment job to fix it. Now, this environment wasn't really mature, and it was very wasn't really mature, and it was very wasn't really mature, and it was very duct tape kind of duct tape kind of duct tape kind of environment. environment. environment. Lots of Linux servers, lots of Ansible, Lots of Linux servers, lots of Ansible, Lots of Linux servers, lots of Ansible, a great place to learn for a great place to learn for a great place to learn for troubleshooting as a junior. So, every troubleshooting as a junior. So, every troubleshooting as a junior. So, every ticket was basically a little quest ticket was basically a little quest ticket was basically a little quest through an undocumented system that had through an undocumented system that had through an undocumented system that had been built over the years, which was been built over the years, which was been built over the years, which was really unstable, and really unstable, and really unstable, and it was a great way for me to learn it was a great way for me to learn it was a great way for me to learn troubleshooting because every ticket troubleshooting because every ticket troubleshooting because every ticket would involve me SSHing into a server, would involve me SSHing into a server, would involve me SSHing into a server, figuring out what was wrong, and there figuring out what was wrong, and there figuring out what was wrong, and there was always random stuff breaking or was always random stuff breaking or was always random stuff breaking or random things that these people needed random things that these people needed random things that these people needed help with. So, it was very reactive, and help with. So, it was very reactive, and help with. So, it was very reactive, and every day was completely different. Now, every day was completely different. Now, every day was completely different. Now, the second part would be the project the second part would be the project the second part would be the project shift, right? The proactive work. And shift, right? The proactive work. And shift, right? The proactive work. And this is where, like a software team, we this is where, like a software team, we this is where, like a software team, we would have a backlog of improvements and would have a backlog of improvements and would have a backlog of improvements and projects to work on, and then in the projects to work on, and then in the projects to work on, and then in the beginning of the sprint, you would be beginning of the sprint, you would be beginning of the sprint, you would be assigned or you would pick a couple of assigned or you would pick a couple of assigned or you would pick a couple of these projects, and that is what you these projects, and that is what you these projects, and that is what you would work on when you did not have would work on when you did not have would work on when you did not have those those those reactive days. So, in this team, we

reactive days. So, in this team, we reactive days. So, in this team, we would split it a week, so you would have would split it a week, so you would have would split it a week, so you would have a week of support work, and then the a week of support work, and then the a week of support work, and then the rest of the sprint you had another week rest of the sprint you had another week rest of the sprint you had another week to focus on your proactive work. That's to focus on your proactive work. That's to focus on your proactive work. That's how we did it. So, at this stage, I was how we did it. So, at this stage, I was how we did it. So, at this stage, I was of course a junior engineer, so I was of course a junior engineer, so I was of course a junior engineer, so I was not able to pick up like huge projects, not able to pick up like huge projects, not able to pick up like huge projects, but there were some very interesting but there were some very interesting but there were some very interesting projects that I got to do there. One of projects that I got to do there. One of projects that I got to do there. One of the main projects I did was to migrate a the main projects I did was to migrate a the main projects I did was to migrate a 4 TB Postgres database to a new server 4 TB Postgres database to a new server 4 TB Postgres database to a new server and upgrade Postgres two major versions. and upgrade Postgres two major versions. and upgrade Postgres two major versions. Now, this that does not sound like a Now, this that does not sound like a Now, this that does not sound like a junior job to do, which it isn't. The junior job to do, which it isn't. The junior job to do, which it isn't. The fact was that in this team where I was fact was that in this team where I was fact was that in this team where I was at, like people were coming and going at, like people were coming and going at, like people were coming and going quite a lot, right? There was lots of quite a lot, right? There was lots of quite a lot, right? There was lots of freelancers, and when I was there, there freelancers, and when I was there, there freelancers, and when I was there, there wasn't anyone with any deep Postgres wasn't anyone with any deep Postgres wasn't anyone with any deep Postgres knowledge. And because I was an knowledge. And because I was an knowledge. And because I was an underpaid junior, they were happy to underpaid junior, they were happy to underpaid junior, they were happy to assign me that task because assign me that task because assign me that task because someone had to do it, and someone had to someone had to do it, and someone had to someone had to do it, and someone had to figure it out. So, I was able to go deep figure it out. So, I was able to go deep figure it out. So, I was able to go deep into Postgres and really figure out how into Postgres and really figure out how into Postgres and really figure out how everything was set up, all of the everything was set up, all of the everything was set up, all of the Ansible playbooks, and how Postgres Ansible playbooks, and how Postgres Ansible playbooks, and how Postgres works essentially. So, I had to figure works essentially. So, I had to figure works essentially. So, I had to figure out how to upgrade those major versions.

out how to upgrade those major versions. out how to upgrade those major versions. I had to do that in a test environment. I had to do that in a test environment. I had to do that in a test environment. I had to orchestrate a migration of a 4 I had to orchestrate a migration of a 4 I had to orchestrate a migration of a 4 TB database, which took well over 24 TB database, which took well over 24 TB database, which took well over 24 hours to even copy over, right? It was hours to even copy over, right? It was hours to even copy over, right? It was really interesting work, and I learned a really interesting work, and I learned a really interesting work, and I learned a ton of ton from that. A second project ton of ton from that. A second project ton of ton from that. A second project that I did was we were not running that I did was we were not running that I did was we were not running Kubernetes, we were running Docker Kubernetes, we were running Docker Kubernetes, we were running Docker containers on VMs that we managed containers on VMs that we managed containers on VMs that we managed ourselves. So, we had like 10 VMs ourselves. So, we had like 10 VMs ourselves. So, we had like 10 VMs running hundreds of Docker containers, running hundreds of Docker containers, running hundreds of Docker containers, but there was no monitoring, no but there was no monitoring, no but there was no monitoring, no observability, and most importantly, no observability, and most importantly, no observability, and most importantly, no security scanning. So, one of the security scanning. So, one of the security scanning. So, one of the projects I did there was I built a projects I did there was I built a projects I did there was I built a completely custom service written in completely custom service written in completely custom service written in Python that would go through these Python that would go through these Python that would go through these servers, take each running container servers, take each running container servers, take each running container that was there, and then perform a that was there, and then perform a that was there, and then perform a security scan on those container images. security scan on those container images. security scan on those container images. It would then generate a report from It would then generate a report from It would then generate a report from that and give us insights into what was that and give us insights into what was that and give us insights into what was running on those running on those running on those servers. And newsflash, there there was servers. And newsflash, there there was servers. And newsflash, there there was a ton of CVEs, and like containers 2 a ton of CVEs, and like containers 2 a ton of CVEs, and like containers 2 years old that never had been updated.

years old that never had been updated. years old that never had been updated. So, it gave us a lot of insight, but So, it gave us a lot of insight, but So, it gave us a lot of insight, but this was a lot of fun to do. It was a this was a lot of fun to do. It was a this was a lot of fun to do. It was a fun project to do because it taught me fun project to do because it taught me fun project to do because it taught me how to code, it taught me how how their how to code, it taught me how how their how to code, it taught me how how their infrastructure worked, and it was infrastructure worked, and it was infrastructure worked, and it was something that I could really dig in and something that I could really dig in and something that I could really dig in and work on for a few weeks. That was my work on for a few weeks. That was my work on for a few weeks. That was my first real implementation of Python first real implementation of Python first real implementation of Python code, and it was a great great learning code, and it was a great great learning code, and it was a great great learning experience. So, that is what I want you experience. So, that is what I want you experience. So, that is what I want you to understand from that that even if you to understand from that that even if you to understand from that that even if you are a junior DevOps engineer, depending are a junior DevOps engineer, depending are a junior DevOps engineer, depending on the environment that you're in, like on the environment that you're in, like on the environment that you're in, like you're not getting coffee for the you're not getting coffee for the you're not getting coffee for the seniors, right? You as a junior seniors, right? You as a junior seniors, right? You as a junior engineer, if you have the the the the engineer, if you have the the the the engineer, if you have the the the the skills and if you had the right mentors, skills and if you had the right mentors, skills and if you had the right mentors, then you can do these production-grade then you can do these production-grade then you can do these production-grade um implementations and tough projects um implementations and tough projects um implementations and tough projects like migrating and upgrading post-class like migrating and upgrading post-class like migrating and upgrading post-class databases even as a junior. Because when databases even as a junior. Because when databases even as a junior. Because when I started out, it was so hard for me to I started out, it was so hard for me to I started out, it was so hard for me to know what to focus on, which tools know what to focus on, which tools know what to focus on, which tools should I learn, how do I even land the should I learn, how do I even land the should I learn, how do I even land the first DevOps job, and where can I get first DevOps job, and where can I get first DevOps job, and where can I get help with this? Well, all of these help with this? Well, all of these help with this? Well, all of these questions will be answered completely questions will be answered completely questions will be answered completely for free in over 20 hours of free for free in over 20 hours of free for free in over 20 hours of free premium video course material that you premium video course material that you premium video course material that you can get completely for free by clicking can get completely for free by clicking can get completely for free by clicking the link in the description box down the link in the description box down the link in the description box down below. It's my gift to you. Best of luck below. It's my gift to you. Best of luck below. It's my gift to you. Best of luck with it. Now, my second job was a with it. Now, my second job was a with it. Now, my second job was a massive step up. So, while I was working massive step up. So, while I was working massive step up. So, while I was working at Amsterdam as a junior, I encountered at Amsterdam as a junior, I encountered at Amsterdam as a junior, I encountered Kubernetes for the first time. We Kubernetes for the first time. We Kubernetes for the first time. We weren't using it then, but I discovered weren't using it then, but I discovered weren't using it then, but I discovered it during my free time, and as soon as I

it during my free time, and as soon as I it during my free time, and as soon as I tried it for the first time, I fell tried it for the first time, I fell tried it for the first time, I fell completely in love with it, and I spent completely in love with it, and I spent completely in love with it, and I spent all my evenings, weekends going deep all my evenings, weekends going deep all my evenings, weekends going deep into Kubernetes and studying it. into Kubernetes and studying it. into Kubernetes and studying it. Eventually, I got certified, and I Eventually, I got certified, and I Eventually, I got certified, and I managed to land a job as a Kubernetes managed to land a job as a Kubernetes managed to land a job as a Kubernetes consultant doubling my current salary. consultant doubling my current salary. consultant doubling my current salary. And one of the first assignments I had And one of the first assignments I had And one of the first assignments I had as a Kubernetes consultant was with the as a Kubernetes consultant was with the as a Kubernetes consultant was with the Dutch National Railways. Here, I joined Dutch National Railways. Here, I joined Dutch National Railways. Here, I joined the cloud platform team, which was the cloud platform team, which was the cloud platform team, which was running on Microsoft Azure. Now, this running on Microsoft Azure. Now, this running on Microsoft Azure. Now, this was a completely different scale. Like was a completely different scale. Like was a completely different scale. Like this team was managing hundreds of Azure this team was managing hundreds of Azure this team was managing hundreds of Azure subscriptions and well over 100 subscriptions and well over 100 subscriptions and well over 100 developer teams as well. It was huge, developer teams as well. It was huge, developer teams as well. It was huge, and that's the scale that we're talking and that's the scale that we're talking and that's the scale that we're talking about here. Because this was a large about here. Because this was a large about here. Because this was a large enterprise like this with much higher enterprise like this with much higher enterprise like this with much higher stakes, the work environment was very stakes, the work environment was very stakes, the work environment was very different. different. different. Like we're talking critical Like we're talking critical Like we're talking critical public transport infrastructure here. public transport infrastructure here. public transport infrastructure here. So, there was a lot more paperwork to be So, there was a lot more paperwork to be So, there was a lot more paperwork to be done, there were much stricter rules, done, there were much stricter rules, done, there were much stricter rules, much more processes, and a very much more processes, and a very much more processes, and a very different environment to be in rather different environment to be in rather different environment to be in rather than this sort of mini startup within a than this sort of mini startup within a than this sort of mini startup within a government organization. And because it government organization. And because it government organization. And because it was such a huge team, there was also a was such a huge team, there was also a was such a huge team, there was also a huge amount of what I call grunt work.

huge amount of what I call grunt work. huge amount of what I call grunt work. So, we had to do a lot of like role So, we had to do a lot of like role So, we had to do a lot of like role assignments. And so, a lot of tickets assignments. And so, a lot of tickets assignments. And so, a lot of tickets that would come in, which basically that would come in, which basically that would come in, which basically involved like changing one line in the involved like changing one line in the involved like changing one line in the code and submitting a PR in code and submitting a PR in code and submitting a PR in like there was hours of toil or or like like there was hours of toil or or like like there was hours of toil or or like boring work that needed to be done, but boring work that needed to be done, but boring work that needed to be done, but the only people who could do it were the the only people who could do it were the the only people who could do it were the DevOps engineers, but they had access to DevOps engineers, but they had access to DevOps engineers, but they had access to the systems. So, that is also a reality the systems. So, that is also a reality the systems. So, that is also a reality of these bigger enterprise environments of these bigger enterprise environments of these bigger enterprise environments that there is also that there is also that there is also work that is not so fun to do. So, many work that is not so fun to do. So, many work that is not so fun to do. So, many hours of the day were not very hours of the day were not very hours of the day were not very glamorous. But, on the other hand, there glamorous. But, on the other hand, there glamorous. But, on the other hand, there were also some really cool projects that were also some really cool projects that were also some really cool projects that I could do there. All of this I could do there. All of this I could do there. All of this infrastructure was handled through Bicep infrastructure was handled through Bicep infrastructure was handled through Bicep templates, and I had been learning Bicep templates, and I had been learning Bicep templates, and I had been learning Bicep in my free time there as well. And here, in my free time there as well. And here, in my free time there as well. And here, I got the chance of developing a I got the chance of developing a I got the chance of developing a completely new disaster recovery completely new disaster recovery completely new disaster recovery environment where I had to build out a environment where I had to build out a environment where I had to build out a full network environment, set up full network environment, set up full network environment, set up multiple multiple firewalls in multiple multiple multiple firewalls in multiple multiple multiple firewalls in multiple regions mirrored from our own live regions mirrored from our own live regions mirrored from our own live production environment, and I had to production environment, and I had to production environment, and I had to write all these Bicep modules and all of write all these Bicep modules and all of write all these Bicep modules and all of these pipelines completely from scratch.

these pipelines completely from scratch. these pipelines completely from scratch. And that was a super cool project that I And that was a super cool project that I And that was a super cool project that I learned so much from because the learned so much from because the learned so much from because the requirements were massive, and I really requirements were massive, and I really requirements were massive, and I really had to dig deep and and build this from had to dig deep and and build this from had to dig deep and and build this from scratch with the help of the architects, scratch with the help of the architects, scratch with the help of the architects, and I learned a ton from that. So, when and I learned a ton from that. So, when and I learned a ton from that. So, when I was not doing this sort of boring I was not doing this sort of boring I was not doing this sort of boring ticket work, I was actually building ticket work, I was actually building ticket work, I was actually building some cool stuff that would have massive some cool stuff that would have massive some cool stuff that would have massive implications for the for the company, implications for the for the company, implications for the for the company, and I was working with some very very and I was working with some very very and I was working with some very very senior intelligent people that I could senior intelligent people that I could senior intelligent people that I could draw a lot from. Now, the second biggest draw a lot from. Now, the second biggest draw a lot from. Now, the second biggest thing that happened during this job, thing that happened during this job, thing that happened during this job, this assignment, was when I joined, I this assignment, was when I joined, I this assignment, was when I joined, I had very little production Kubernetes had very little production Kubernetes had very little production Kubernetes experience. I had done the studies. I experience. I had done the studies. I experience. I had done the studies. I hadn't had the chance of getting much hadn't had the chance of getting much hadn't had the chance of getting much experience, and when I joined, we were experience, and when I joined, we were experience, and when I joined, we were running over 50 Azure Kubernetes running over 50 Azure Kubernetes running over 50 Azure Kubernetes clusters already. Now, the person who clusters already. Now, the person who clusters already. Now, the person who was responsible for managing those was responsible for managing those was responsible for managing those clusters, he was scheduled to leave. So, clusters, he was scheduled to leave. So, clusters, he was scheduled to leave. So, I I I like very assertively came in and and like very assertively came in and and like very assertively came in and and said, "I I want to take this over." So, said, "I I want to take this over." So, said, "I I want to take this over." So, there was a bit of a transition period, there was a bit of a transition period, there was a bit of a transition period, but I went from having zero Kubernetes but I went from having zero Kubernetes but I went from having zero Kubernetes experience to being Mr. Kubernetes at experience to being Mr. Kubernetes at experience to being Mr. Kubernetes at the Dutch National Railways. I I I it the Dutch National Railways. I I I it the Dutch National Railways. I I I it went very quickly went very quickly went very quickly because I was throwing myself into work because I was throwing myself into work because I was throwing myself into work that was honestly above my pay grade, that was honestly above my pay grade, that was honestly above my pay grade, but that also forced me to learn and to but that also forced me to learn and to but that also forced me to learn and to grow very quickly. So, when I was thrown grow very quickly. So, when I was thrown grow very quickly. So, when I was thrown into an an incident or when something into an an incident or when something into an an incident or when something needed to be updated or or or fixed, I

needed to be updated or or or fixed, I needed to be updated or or or fixed, I had the the knowledge and the skills, had the the knowledge and the skills, had the the knowledge and the skills, but I had didn't have the experience. but I had didn't have the experience. but I had didn't have the experience. So, I would go all in on it, and yeah, So, I would go all in on it, and yeah, So, I would go all in on it, and yeah, frankly, I I would work deep into the frankly, I I would work deep into the frankly, I I would work deep into the night in my own time to fix these things night in my own time to fix these things night in my own time to fix these things because this was my chance to grow. So, because this was my chance to grow. So, because this was my chance to grow. So, I didn't really think about work hours. I didn't really think about work hours. I didn't really think about work hours. I just took it as the opportunity to get I just took it as the opportunity to get I just took it as the opportunity to get this experience. Because I didn't work this experience. Because I didn't work this experience. Because I didn't work my 8 hours a day, but I was working my 8 hours a day, but I was working my 8 hours a day, but I was working double that, I very quickly went from double that, I very quickly went from double that, I very quickly went from zero to Mr. Kubernetes in the zero to Mr. Kubernetes in the zero to Mr. Kubernetes in the organization. So, when I took over, the organization. So, when I took over, the organization. So, when I took over, the first thing I noticed was that we were first thing I noticed was that we were first thing I noticed was that we were we were two minor versions behind, which we were two minor versions behind, which we were two minor versions behind, which is a big sin in the Kubernetes world is a big sin in the Kubernetes world is a big sin in the Kubernetes world because as you know, every 6 months, because as you know, every 6 months, because as you know, every 6 months, there is a new release, and Azure there is a new release, and Azure there is a new release, and Azure Kubernetes service will actually stop Kubernetes service will actually stop Kubernetes service will actually stop supporting you if you are two minor supporting you if you are two minor supporting you if you are two minor versions behind. So, you have to be very versions behind. So, you have to be very versions behind. So, you have to be very very up-to-date all the time if you want very up-to-date all the time if you want very up-to-date all the time if you want to get the continuous support from to get the continuous support from to get the continuous support from Microsoft. The person who was in charge Microsoft. The person who was in charge Microsoft. The person who was in charge hadn't followed up with this. So, the hadn't followed up with this. So, the hadn't followed up with this. So, the the clusters were actually getting out the clusters were actually getting out the clusters were actually getting out of date. So, this was the first thing of date. So, this was the first thing of date. So, this was the first thing that I took over. Now, that I took over. Now, that I took over. Now, to give you an indication, like these to give you an indication, like these to give you an indication, like these were not toy applications that were were not toy applications that were were not toy applications that were running here. One of the applications running here. One of the applications running here. One of the applications that I managed, or the cluster rather I that I managed, or the cluster rather I that I managed, or the cluster rather I managed that was running the managed that was running the managed that was running the application, was an application for bike application, was an application for bike application, was an application for bike parking. So, in the Netherlands, 1.1 parking. So, in the Netherlands, 1.1 parking. So, in the Netherlands, 1.1 million people travel by train every million people travel by train every million people travel by train every day, and the majority of these people day, and the majority of these people day, and the majority of these people will take their bicycle and cycle to the will take their bicycle and cycle to the will take their bicycle and cycle to the train station, and then there is this

train station, and then there is this train station, and then there is this large automated facility where you can large automated facility where you can large automated facility where you can park your bicycle in a guarded facility. park your bicycle in a guarded facility. park your bicycle in a guarded facility. Now, to get into that facility, you take Now, to get into that facility, you take Now, to get into that facility, you take your public transport card and scan it your public transport card and scan it your public transport card and scan it at one of these little gates. at one of these little gates. at one of these little gates. Now, when you scan at that gate, that Now, when you scan at that gate, that Now, when you scan at that gate, that signal would go to the Kubernetes signal would go to the Kubernetes signal would go to the Kubernetes cluster that I was managing. It would be cluster that I was managing. It would be cluster that I was managing. It would be processed there and sent back, and that processed there and sent back, and that processed there and sent back, and that is how the access was granted. So, if is how the access was granted. So, if is how the access was granted. So, if that application went down, that application went down, that application went down, 1.1 million people would not be able to 1.1 million people would not be able to 1.1 million people would not be able to park their bikes in these facilities or park their bikes in these facilities or park their bikes in these facilities or get their bikes out. So, in that sense, get their bikes out. So, in that sense, get their bikes out. So, in that sense, this was critical infrastructure, and I this was critical infrastructure, and I this was critical infrastructure, and I was managing the cluster that was was managing the cluster that was was managing the cluster that was running this application. And this is running this application. And this is running this application. And this is just one example, but there were all just one example, but there were all just one example, but there were all sorts of train-related public sorts of train-related public sorts of train-related public infrastructure that I was managing on infrastructure that I was managing on infrastructure that I was managing on these clusters. So, when you then start these clusters. So, when you then start these clusters. So, when you then start upgrading this cluster, you better be upgrading this cluster, you better be upgrading this cluster, you better be sure that this goes well, right? So, I sure that this goes well, right? So, I sure that this goes well, right? So, I had to go in, I had to do a lot of had to go in, I had to do a lot of had to go in, I had to do a lot of talking with the engineers. We had to talking with the engineers. We had to talking with the engineers. We had to like submit a lot of paperwork in order like submit a lot of paperwork in order like submit a lot of paperwork in order to be allowed to do an upgrade. It was to be allowed to do an upgrade. It was to be allowed to do an upgrade. It was actually a lot of paperwork. So, that's actually a lot of paperwork. So, that's actually a lot of paperwork. So, that's also the reality of an enterprise also the reality of an enterprise also the reality of an enterprise environment, but I learned so much.

environment, but I learned so much. environment, but I learned so much. There were there were incidents that There were there were incidents that There were there were incidents that some of these upgrades, they went fine some of these upgrades, they went fine some of these upgrades, they went fine on staging, and then they failed in on staging, and then they failed in on staging, and then they failed in production, and we had to do these production, and we had to do these production, and we had to do these upgrades late in the night because upgrades late in the night because upgrades late in the night because obviously then fewer people are using the trains, so we were are using the trains, so we were required to do Now, I've been in required to do Now, I've been in required to do Now, I've been in situations where a production situations where a production situations where a production application like that did not come up application like that did not come up application like that did not come up after the upgrade, and there was after the upgrade, and there was after the upgrade, and there was literally no difference between staging literally no difference between staging literally no difference between staging and production. But, this is when the and production. But, this is when the and production. But, this is when the real learning happens, right? You are real learning happens, right? You are real learning happens, right? You are sitting there, you're sweating, the sitting there, you're sweating, the sitting there, you're sweating, the application is not up and running, but application is not up and running, but application is not up and running, but the application better be up and running the application better be up and running the application better be up and running at 5:00 a.m. in the morning because at 5:00 a.m. in the morning because at 5:00 a.m. in the morning because that's when people are going to be start that's when people are going to be start that's when people are going to be start starting to park their bikes, right? And starting to park their bikes, right? And starting to park their bikes, right? And every single time we got it to work, but every single time we got it to work, but every single time we got it to work, but the quickest way to learn something is the quickest way to learn something is the quickest way to learn something is to take control of a big project like to take control of a big project like to take control of a big project like that and actually finish it. So, yeah, I that and actually finish it. So, yeah, I that and actually finish it. So, yeah, I did successfully do it. I became Mr.

did successfully do it. I became Mr. did successfully do it. I became Mr. Kubernetes, and I learned a lot in this Kubernetes, and I learned a lot in this Kubernetes, and I learned a lot in this in this role. But, as you can see, this in this role. But, as you can see, this in this role. But, as you can see, this role was much more higher stakes, with role was much more higher stakes, with role was much more higher stakes, with much more enterprise, a lot of focus on much more enterprise, a lot of focus on much more enterprise, a lot of focus on on on on building like large structures from building like large structures from building like large structures from scratch or doing very very challenging scratch or doing very very challenging scratch or doing very very challenging maintenance tasks. So, this was an maintenance tasks. So, this was an maintenance tasks. So, this was an environment with a lot of contrast. It environment with a lot of contrast. It environment with a lot of contrast. It was was was many hours of quite boring admin work many hours of quite boring admin work many hours of quite boring admin work with paperwork or doing boring support with paperwork or doing boring support with paperwork or doing boring support tickets, but then the balance was that tickets, but then the balance was that tickets, but then the balance was that there was there were also some very there was there were also some very there was there were also some very exciting and challenging situations when exciting and challenging situations when exciting and challenging situations when something went wrong or there is an something went wrong or there is an something went wrong or there is an incident or something like that. So, if incident or something like that. So, if incident or something like that. So, if you're enjoying these stories so far, you're enjoying these stories so far, you're enjoying these stories so far, please click the subscribe button down please click the subscribe button down please click the subscribe button down below if you haven't already. And now, below if you haven't already. And now, below if you haven't already. And now, I'll share what my third job looked I'll share what my third job looked I'll share what my third job looked like, and this job was at a company like, and this job was at a company like, and this job was at a company called Van Oord. called Van Oord. called Van Oord. This is a marine company, and these are This is a marine company, and these are This is a marine company, and these are the people who built the Palm Islands in the people who built the Palm Islands in the people who built the Palm Islands in Dubai, for example. They specialize in Dubai, for example. They specialize in Dubai, for example. They specialize in building windmill parks in the in the building windmill parks in the in the building windmill parks in the in the sea, but also dredging. So, taking soil sea, but also dredging. So, taking soil sea, but also dredging. So, taking soil from the bottom of the sea and putting from the bottom of the sea and putting from the bottom of the sea and putting it elsewhere so that the ships can go it elsewhere so that the ships can go it elsewhere so that the ships can go through. And this was a really through. And this was a really through. And this was a really interesting environment. So, I joined interesting environment. So, I joined interesting environment. So, I joined their cloud platform team, and there their cloud platform team, and there their cloud platform team, and there there was quite a difference because at there was quite a difference because at there was quite a difference because at the train company, yes, we were using the train company, yes, we were using the train company, yes, we were using Kubernetes, but it wasn't very mature.

Kubernetes, but it wasn't very mature. Kubernetes, but it wasn't very mature. Some teams were using Terraform to apply Some teams were using Terraform to apply Some teams were using Terraform to apply the manifests or just pushing manifests the manifests or just pushing manifests the manifests or just pushing manifests to it. It It was quite messy many of the to it. It It was quite messy many of the to it. It It was quite messy many of the times, but this stack was actually a lot times, but this stack was actually a lot times, but this stack was actually a lot more mature in in terms of cloud native. more mature in in terms of cloud native. more mature in in terms of cloud native. So, we were using Argo CD, Azure So, we were using Argo CD, Azure So, we were using Argo CD, Azure Kubernetes, proper pipelines. It was Kubernetes, proper pipelines. It was Kubernetes, proper pipelines. It was much more mature that way, but the much more mature that way, but the much more mature that way, but the problem was the infrastructure was problem was the infrastructure was problem was the infrastructure was mature, but the teams using it were not mature, but the teams using it were not mature, but the teams using it were not that mature. They were not that routined that mature. They were not that routined that mature. They were not that routined with it yet. So, this gave some very with it yet. So, this gave some very with it yet. So, this gave some very interesting challenges that I'm going to interesting challenges that I'm going to interesting challenges that I'm going to talk about in a second. So, the talk about in a second. So, the talk about in a second. So, the infrastructure was mature, but the infrastructure was mature, but the infrastructure was mature, but the challenge here wasn't really the challenge here wasn't really the challenge here wasn't really the infrastructure, it was the people. So, infrastructure, it was the people. So, infrastructure, it was the people. So, we had we had built this beautiful we had we had built this beautiful we had we had built this beautiful platform with all of these workflows, platform with all of these workflows, platform with all of these workflows, but the developer teams weren't really but the developer teams weren't really but the developer teams weren't really using it as intended. And an example of using it as intended. And an example of using it as intended. And an example of this would be that like many teams did this would be that like many teams did this would be that like many teams did not have auto sync on in their Argo CD not have auto sync on in their Argo CD not have auto sync on in their Argo CD workflows. They would push their their workflows. They would push their their workflows. They would push their their changes to the repo, and then they would changes to the repo, and then they would changes to the repo, and then they would ask us, "Please sync the repo." because ask us, "Please sync the repo." because ask us, "Please sync the repo." because they didn't dare to do it themselves.

they didn't dare to do it themselves. they didn't dare to do it themselves. So, the adoption was lagging a lot, and So, the adoption was lagging a lot, and So, the adoption was lagging a lot, and this this gave some very interesting this this gave some very interesting this this gave some very interesting challenges. challenges. challenges. There was also situations where like There was also situations where like There was also situations where like developers were using CSV files on Azure developers were using CSV files on Azure developers were using CSV files on Azure file shares, where this this stuff file shares, where this this stuff file shares, where this this stuff should have been in databases long ago, should have been in databases long ago, should have been in databases long ago, right? So, there was a lot of technical right? So, there was a lot of technical right? So, there was a lot of technical education and adoption to be done here. education and adoption to be done here. education and adoption to be done here. So, after a while, I was actually So, after a while, I was actually So, after a while, I was actually spending most of my time being in spending most of my time being in spending most of my time being in meetings with stakeholders, with meetings with stakeholders, with meetings with stakeholders, with developer teams, and engineers developer teams, and engineers developer teams, and engineers to to actually educate them on the to to actually educate them on the to to actually educate them on the platform that we had. We had all of this platform that we had. We had all of this platform that we had. We had all of this cool stuff, but people were not using cool stuff, but people were not using cool stuff, but people were not using it. One example was that we were having it. One example was that we were having it. One example was that we were having Kubernetes clusters, which of course is Kubernetes clusters, which of course is Kubernetes clusters, which of course is built to scale, but we had these big built to scale, but we had these big built to scale, but we had these big clusters that were running almost clusters that were running almost clusters that were running almost completely under utilized. And the completely under utilized. And the completely under utilized. And the applications that were running on there, applications that were running on there, applications that were running on there, they were not built for cloud native they were not built for cloud native they were not built for cloud native infrastructure. They were not built to infrastructure. They were not built to infrastructure. They were not built to scale. So, when you have an application scale. So, when you have an application scale. So, when you have an application that has batch jobs, for example, then that has batch jobs, for example, then that has batch jobs, for example, then it doesn't make sense to have all of the it doesn't make sense to have all of the it doesn't make sense to have all of the workers online all the time. This is why workers online all the time. This is why workers online all the time. This is why Kubernetes is so great because you can Kubernetes is so great because you can Kubernetes is so great because you can scale out your infrastructure when you scale out your infrastructure when you scale out your infrastructure when you need the capacity for running these need the capacity for running these need the capacity for running these batch jobs, but when these batch jobs batch jobs, but when these batch jobs batch jobs, but when these batch jobs are not running, you have to scale it are not running, you have to scale it are not running, you have to scale it down. So, one of the tasks I did was to down. So, one of the tasks I did was to down. So, one of the tasks I did was to implement KEDA, Kubernetes event-driven implement KEDA, Kubernetes event-driven implement KEDA, Kubernetes event-driven auto scaling on these applications, and

auto scaling on these applications, and auto scaling on these applications, and then implementing that on our Kubernetes then implementing that on our Kubernetes then implementing that on our Kubernetes clusters. clusters. clusters. So, this was a really cool project to So, this was a really cool project to So, this was a really cool project to do, to take an application, observing do, to take an application, observing do, to take an application, observing that it was running all the time, and that it was running all the time, and that it was running all the time, and with the developers then with the developers then with the developers then taking the implementing auto scaling, taking the implementing auto scaling, taking the implementing auto scaling, and then bringing that live on the and then bringing that live on the and then bringing that live on the clusters. It was It was a really clusters. It was It was a really clusters. It was It was a really interesting project. So, it was a lot of interesting project. So, it was a lot of interesting project. So, it was a lot of guidance and teaching people how to do guidance and teaching people how to do guidance and teaching people how to do this in this in this type of role. But this in this in this type of role. But this in this in this type of role. But there were also less comfortable there were also less comfortable there were also less comfortable situations. So, for example, this CSV situations. So, for example, this CSV situations. So, for example, this CSV example that I mentioned, like I really example that I mentioned, like I really example that I mentioned, like I really had to show how much slower this this had to show how much slower this this had to show how much slower this this situation was that they had. Where you situation was that they had. Where you situation was that they had. Where you we were reading stuff with Python from we were reading stuff with Python from we were reading stuff with Python from CSV files on a file share, and they CSV files on a file share, and they CSV files on a file share, and they would have one file share with would have one file share with would have one file share with everything dumped into one file share, everything dumped into one file share, everything dumped into one file share, and staging production, they were all and staging production, they were all and staging production, they were all taking from the same file share. Like taking from the same file share. Like taking from the same file share. Like there were some some things there that there were some some things there that there were some some things there that should not be in in production. And I should not be in in production. And I should not be in in production. And I really had to educate them on this and really had to educate them on this and really had to educate them on this and and and make them aware of the security and and make them aware of the security and and make them aware of the security issues, the performance issues that we issues, the performance issues that we issues, the performance issues that we were having. When you come in as a were having. When you come in as a were having. When you come in as a consultant like that, and you and you consultant like that, and you and you consultant like that, and you and you just say, "Yeah, we have to move this to just say, "Yeah, we have to move this to just say, "Yeah, we have to move this to databases."

databases." databases." the reaction is, "Whoa whoa the reaction is, "Whoa whoa the reaction is, "Whoa whoa Hold on here, cowboy. Um we don't have Hold on here, cowboy. Um we don't have Hold on here, cowboy. Um we don't have these database skills in the team. We these database skills in the team. We these database skills in the team. We don't have the competence. We It would don't have the competence. We It would don't have the competence. We It would take too much time to learn." Yeah, all take too much time to learn." Yeah, all take too much time to learn." Yeah, all of it is not that hard when you sit down of it is not that hard when you sit down of it is not that hard when you sit down and just do it, right? This is why soft and just do it, right? This is why soft and just do it, right? This is why soft skills are so important in DevOps, where skills are so important in DevOps, where skills are so important in DevOps, where you actually have to convince stake you actually have to convince stake you actually have to convince stake holders and managers to free up some holders and managers to free up some holders and managers to free up some time to do this because there are so time to do this because there are so time to do this because there are so many security and performance benefits many security and performance benefits many security and performance benefits to these kinds of things. So, this role to these kinds of things. So, this role to these kinds of things. So, this role really taught me a very critical thing really taught me a very critical thing really taught me a very critical thing that most people overlook, which is that that most people overlook, which is that that most people overlook, which is that DevOps is not just a technical role DevOps is not just a technical role DevOps is not just a technical role where you're either SSHing and and where you're either SSHing and and where you're either SSHing and and troubleshooting, or you're building troubleshooting, or you're building troubleshooting, or you're building these cool projects. Proper DevOps these cool projects. Proper DevOps these cool projects. Proper DevOps roles, in this case it was a platform roles, in this case it was a platform roles, in this case it was a platform engineering role, engineering role, engineering role, really requires you to have good soft really requires you to have good soft really requires you to have good soft skills, where you are able to to break skills, where you are able to to break skills, where you are able to to break down complex tasks and communicate those down complex tasks and communicate those down complex tasks and communicate those to stakeholders who are not technical. to stakeholders who are not technical. to stakeholders who are not technical. That is an extremely important skill That is an extremely important skill That is an extremely important skill that you need to learn if you want to be that you need to learn if you want to be that you need to learn if you want to be a successful DevOps engineer. It's not a successful DevOps engineer. It's not a successful DevOps engineer. It's not just about sitting and coding in your just about sitting and coding in your just about sitting and coding in your room. There is a lot of social room. There is a lot of social room. There is a lot of social interaction that needs to happen as interaction that needs to happen as interaction that needs to happen as well. That being said, there was a lot well. That being said, there was a lot well. That being said, there was a lot of cool technical work that I did there of cool technical work that I did there of cool technical work that I did there as well. The first thing was that we as well. The first thing was that we as well. The first thing was that we were running Postgres databases on were running Postgres databases on were running Postgres databases on Kubernetes clusters. So, this is where I Kubernetes clusters. So, this is where I Kubernetes clusters. So, this is where I learned how to learned how to learned how to deploy and manage and maintain deploy and manage and maintain deploy and manage and maintain databases on Kubernetes using the databases on Kubernetes using the databases on Kubernetes using the CloudNativePG or the EnterpriseDB CloudNativePG or the EnterpriseDB CloudNativePG or the EnterpriseDB operators. Um this was I mean, I had my

operators. Um this was I mean, I had my operators. Um this was I mean, I had my Postgres experience from my first role Postgres experience from my first role Postgres experience from my first role that I shared with you, but here I was that I shared with you, but here I was that I shared with you, but here I was bringing that to Kubernetes. So, that bringing that to Kubernetes. So, that bringing that to Kubernetes. So, that was a extremely interesting was a extremely interesting was a extremely interesting um area to work with, and I absolutely um area to work with, and I absolutely um area to work with, and I absolutely loved doing it. And to this day, I'm loved doing it. And to this day, I'm loved doing it. And to this day, I'm using these these using these these using these these um um um operators in my home lab and other work operators in my home lab and other work operators in my home lab and other work assignments as well. But the coolest assignments as well. But the coolest assignments as well. But the coolest thing about this job was that we were thing about this job was that we were thing about this job was that we were running Kubernetes clusters on these running Kubernetes clusters on these running Kubernetes clusters on these ships themselves. So, we had a massive ships themselves. So, we had a massive ships themselves. So, we had a massive fleet of ships all over the world fleet of ships all over the world fleet of ships all over the world connected with the internet over connected with the internet over connected with the internet over satellite, and on each ship there would satellite, and on each ship there would satellite, and on each ship there would be a mini data center, essentially, be a mini data center, essentially, be a mini data center, essentially, because there's actually a lot of IT because there's actually a lot of IT because there's actually a lot of IT that's happening on a ship of that size. that's happening on a ship of that size. that's happening on a ship of that size. And we were also running Kubernetes And we were also running Kubernetes And we were also running Kubernetes clusters on those ships. So, some of the clusters on those ships. So, some of the clusters on those ships. So, some of the days would be to wake up, log in, and days would be to wake up, log in, and days would be to wake up, log in, and then which ship am I updating today? And then which ship am I updating today? And then which ship am I updating today? And you could actually look it up on the you could actually look it up on the you could actually look it up on the map, and maybe it was like sailing in map, and maybe it was like sailing in map, and maybe it was like sailing in the South Pacific somewhere, the South Pacific somewhere, the South Pacific somewhere, and I would have to then upgrade the and I would have to then upgrade the and I would have to then upgrade the Kubernetes cluster on that ship. It was Kubernetes cluster on that ship. It was Kubernetes cluster on that ship. It was wild. It was wild to think that you wild. It was wild to think that you wild. It was wild to think that you would be connecting to a ship sailing would be connecting to a ship sailing would be connecting to a ship sailing somewhere in the ocean and actually somewhere in the ocean and actually somewhere in the ocean and actually talking to the pods on the Kubernetes talking to the pods on the Kubernetes talking to the pods on the Kubernetes cluster there. It was really, really cluster there. It was really, really cluster there. It was really, really cool. And what was interesting was that cool. And what was interesting was that cool. And what was interesting was that you actually had to take the time zones you actually had to take the time zones you actually had to take the time zones into account into account into account because um on the ship, when the sailors because um on the ship, when the sailors because um on the ship, when the sailors were off shift, they would all be like were off shift, they would all be like were off shift, they would all be like watching Netflix or or whatever sailors watching Netflix or or whatever sailors watching Netflix or or whatever sailors do on on ships using internet. You would

do on on ships using internet. You would do on on ships using internet. You would notice that the the connection was very notice that the the connection was very notice that the the connection was very laggy and buggy. So, you would have to laggy and buggy. So, you would have to laggy and buggy. So, you would have to wait until that was over. And sometimes, wait until that was over. And sometimes, wait until that was over. And sometimes, when you could see on the map if the when you could see on the map if the when you could see on the map if the ship was sailing southwards, the um ship was sailing southwards, the um ship was sailing southwards, the um connection would be really bad, but if connection would be really bad, but if connection would be really bad, but if it was sailing northwards, it would it was sailing northwards, it would it was sailing northwards, it would actually be a much better connection. actually be a much better connection. actually be a much better connection. So, you had to take all of these things So, you had to take all of these things So, you had to take all of these things into account when you were timing your into account when you were timing your into account when you were timing your upgrade. It was very interesting to do upgrade. It was very interesting to do upgrade. It was very interesting to do that kind of work. So, that was the that kind of work. So, that was the that kind of work. So, that was the probably the coolest part of that whole probably the coolest part of that whole probably the coolest part of that whole job there that I upgraded Kubernetes job there that I upgraded Kubernetes job there that I upgraded Kubernetes clusters all over the world clusters all over the world clusters all over the world on ships that were basically everywhere. on ships that were basically everywhere. on ships that were basically everywhere. Really cool. So, that's it. That's what Really cool. So, that's it. That's what Really cool. So, that's it. That's what a DevOps career can look like. You can a DevOps career can look like. You can a DevOps career can look like. You can be SSHing into Linux servers, you can be be SSHing into Linux servers, you can be be SSHing into Linux servers, you can be sweating doing sweating doing sweating doing upgrades at 1:00 a.m. in the morning, or upgrades at 1:00 a.m. in the morning, or upgrades at 1:00 a.m. in the morning, or you can be in in heavy discussions with you can be in in heavy discussions with you can be in in heavy discussions with developers who refuse to adopt your developers who refuse to adopt your developers who refuse to adopt your platform. It can be very wide. So, platform. It can be very wide. So, platform. It can be very wide. So, that's why I wanted to share in depth that's why I wanted to share in depth that's why I wanted to share in depth what these days in the life looked like what these days in the life looked like what these days in the life looked like because I think that not not many people because I think that not not many people because I think that not not many people actually are able to paint this picture.

actually are able to paint this picture. actually are able to paint this picture. So, I have had many different jobs in So, I have had many different jobs in So, I have had many different jobs in many different environments because I've many different environments because I've many different environments because I've worked as a consultant for many years, worked as a consultant for many years, worked as a consultant for many years, and this gave me exposure to many types and this gave me exposure to many types and this gave me exposure to many types of environments, which also of environments, which also of environments, which also um which I grew a lot from. This is why um which I grew a lot from. This is why um which I grew a lot from. This is why I went from from nurse to senior DevOps I went from from nurse to senior DevOps I went from from nurse to senior DevOps engineer in such a short time because I engineer in such a short time because I engineer in such a short time because I worked all day, in the evening, and in worked all day, in the evening, and in worked all day, in the evening, and in the weekends. I never stopped, and the weekends. I never stopped, and the weekends. I never stopped, and because I consciously put myself in because I consciously put myself in because I consciously put myself in these challenging environments. So, all these challenging environments. So, all these challenging environments. So, all of these learnings that I got from this of these learnings that I got from this of these learnings that I got from this from these environments, I put them all from these environments, I put them all from these environments, I put them all in the free DevOps career blueprint in the free DevOps career blueprint in the free DevOps career blueprint course. If you're interested in landing course. If you're interested in landing course. If you're interested in landing a DevOps role, you can get this a DevOps role, you can get this a DevOps role, you can get this completely for free. It contains over 20 completely for free. It contains over 20 completely for free. It contains over 20 hours of premium video course material. hours of premium video course material. hours of premium video course material. You can find it in the description box You can find it in the description box You can find it in the description box below or in the pinned comment. It is below or in the pinned comment. It is below or in the pinned comment. It is completely for free. Check it out completely for free. Check it out completely for free. Check it out because I'm sure that it will help you. because I'm sure that it will help you. because I'm sure that it will help you. When I was in the beginning, I really When I was in the beginning, I really When I was in the beginning, I really struggled with knowing what to do, what struggled with knowing what to do, what struggled with knowing what to do, what to focus on, which tools to learn, and to focus on, which tools to learn, and to focus on, which tools to learn, and all of these questions are answered in all of these questions are answered in all of these questions are answered in the free DevOps career blueprint course the free DevOps career blueprint course the free DevOps career blueprint course that you can get by clicking the link that you can get by clicking the link that you can get by clicking the link down below. Check it out. Thank you so down below. Check it out. Thank you so down below. Check it out. Thank you so much for watching this video. Let me much for watching this video. Let me much for watching this video. Let me know what you think. Does this sound know what you think. Does this sound know what you think. Does this sound interesting to you? Did this give you a interesting to you? Did this give you a interesting to you? Did this give you a new insight into what a day in the life new insight into what a day in the life new insight into what a day in the life of a DevOps engineer might look like?

of a DevOps engineer might look like? of a DevOps engineer might look like? And I'll read it in the comments. Let me And I'll read it in the comments. Let me And I'll read it in the comments. Let me know, and thank you so much, and I'll know, and thank you so much, and I'll know, and thank you so much, and I'll see you in the next video.