Opinions on Resume for Jr. DevOps Engineer

Hey guys,

I'm a systems administrator that wants to move into a Jr. DevOps Engineer position. Based on ideas I've gotten from other similar posts in this subreddit, I created my own resume outlining relevant experiences and training. I'd like to get your opinion about my resume. I have of course sanitized personal info and company names.

A couple of notes:
\- My latest experience (company C) is my weakest one. I'm basically a network support guy, not much room for big problems that I solved or systems I implemented. What I want to get across from this entry is that I interacted frequently with software developers, I'm familiar with the extend of their IT infrastructure knowledge and with some of the tools/platforms they use. I can bridge the gap between their needs and lower level networking stuff.
\- There are many tools with which I have training and certs, but not necessarily professional experience, for example Terraform, Jenkins, Openshift. I include these in the technical skills sections pretty much as a list of buzzwords. I know the hiring person will want to know my level of proficiency with these, how would you go about this without cluttering up the resume?

Any feedback is appreciated !

https://imgur.com/qgIgUhP

https://redd.it/12fby1y
@r_devops

file copy to S3

I am looking for a solution to a situation where a user wants to save a file to a network share from their Windows laptop, and I aim to copy the file to an AWS S3 bucket as soon as it is saved to the network share.

What type of network share can I provision ? and how do I achieve this goal, and can you suggest any solution approach?

There are a few limitations to consider in the approach.

Limitation:

1. I do not want to create an EC2 instance for this purpose as it is expensive and not necessary since there is no computation other than just network share.

2. The network share should be accessible to the user Laptop via the SMB or CISF protocol. I checked AWS EFS does not support SMB protocols and it is not for Windows.

3. I can not add AWS credentials to the user's laptop

4. I do not want to use any external commercial products.



Can you suggest any cost-effective solution with these limitations ?

https://redd.it/12fd48c
@r_devops

What are the real cons of using jenkins?

So far I have used Github Actions and (to an extent) Gitlab, so I don't have any Jenkins experience.

I have often read that Jenkins is a nightmare, but I would like to understand more from people who have actually used it.

Is it the plugin system? The Groovy pipeline syntax? Something else entirely? All of the above?

https://redd.it/12fhdkm
@r_devops

Use EC2 as ad-hoc node in on-prem k8s cluster

(I am noobish in this topic so I am sorry in advance if this is a stupid question).

We have on-prem k8s cluster but for some computation I would like to use AWS (EC2). I was thinking if it is possible to add EC2 to our existing cluster anyhow? Ideally it should work like this: I create a pod which should have specified that it has to run on EC2. K8s go and create the EC2 instance and then run the workload on it and after job is done it shutdowns the EC2.

Why: we need to run some data jobs and currently we are creating and deleting the EC2 in Airflow but 1) it requires some overhead (like create, start, await, stop, terminate steps) and 2) it could be tricky to really ALWAYS run the stop/terminate tasks so the EC2 does not run after the job is done.

Is something like this feasible?

https://redd.it/12fi8sm
@r_devops

GHA Actions from Marketplace vs Jenkins Plugins

For context, I’ve been at my org longer than most of the other engineers and managers and have a ton of knowledge around the domain and political landscape. Just started on the “Infra” team full time at the beginning of Q1. All that to say I’m the least experienced on the team around “ops”, but been building tools and automation for the better part of a decade.

We’ve invested hard in GHA this year, mainly because our Jenkins situation is a mess - the plug-in ecosystem is unsustainable and we’ve essentially painted ourselves into a corner over the years where updating Jenkins is risky.

That said, I found myself in a situation this week where a (very hostile) EM was fired up because a GHA pipeline I had built failed for one of his devs. I’m a fan of “eating my own dog food” so I wrote up a bug and set out to fix it immediately.

Upon investigation I discovered the root cause was a bug in an action from the marketplace (from Docker), which I was directed to use by a senior eng after submitting my PR that originally did the same thing via the shell (build, tag and push to ECR).

Of course the EM didn’t care about the details about the bug in the action (and I didn’t mention anything re: being directed to use the action), as far as he was concerned was that my work personally was “impacting productivity” and blah blah blah…

In my case, I feel like the direction from the sr eng on my team was to make the workflow yaml “look clean”, but IMO effectively turned out to be an over-engineered solution.

All that to say is, I feel like the pattern of depending on these marketplace actions without thought or consideration of their impacts (or how to maintain them) is almost no different than relying on the Jenkins plugins?

I don’t really want to push back on the Sr Eng in particular- he’s taught me a TON, but I do think there’s a case to be made about over engineering simple solutions / finding ourselves in a similar situation as Jenkins plug-ins.

Am I over-analyzing this? Curios about other people’s opinions / perspectives.

https://redd.it/12fmkgf
@r_devops

Up to $1000 to spend on "professional development". How would you spend it?

TL;DR - How should I spend up to $1000 of the company's money on professional development, aside from more cloud training? Doesn't have to be completely technical training.

​

I have up to $1000 to spend on any "professional development". I see my next career step to be locking down an infrastructure engineering role that is focused on extending traditional infrastructure to cloud, build/deployment automation, and participating in a team/company with an established cloud/devops strategy in a way that is meaningful to the business.

​

My background over 20+ years:

Extensive experience building and supporting on-prem infrastructure (VMware vSphere, traditional Windows-based infrastructure, storage, hyper-converged, some networking)

Extensive experience with Windows Server and RHEL

Extensive experience using Ansible to configure and/or build/deploy of any of the above (some limited experience with Automation Platform)

Limited experience with implementing AWS storage, EC2, RDS, VPC for small projects, including integration with on-prem network.

Experience designing AWS infrastructure and security for a POC of a cloud app (did not see project through to completion due loss of developers)

Proficiency using Powershell, competent using python and Bash. I have made a couple of minor contributions to an OSS python project. I am comfortable consuming APIs and can read and understand object oriented code.

Experience using git (gitlab/github) to manage personal projects that support my company and my personal development outside of work

Very limited experience building and consuming containers (no orchestration experience outside of classroom)

I have an alphabet soup of various certifications that I have picked up over the years (VMware, Red Hat, MS, AWS, etc)

​

My gaps:

No experience performing any of the above "at scale" - mostly in companies with < 500 servers and < 2000 employees in legacy architecture

No experience working in an organization with top IT leadership pushing for modernization or remotely understanding why an actual strategy for cloud is important

No CI/CD experience at all

Container experience limited to internal projects running standalone/rootless podman, no orchestration and nothing supporting the business


Mini-rant:

I recently transferred from a small IT team at a child company to a much larger infrastructure Engineering team in the parent org (very, very large global company). I was promised by upper management some project work to improve automation and delivery time of server builds, and working on projects that are motivated by a rush modernize the IT landscape, including leveraging the cloud more. However, full on-boarding to my new team has been delayed (still dealing with transition/handover from child company stuff), and my new team manager is obstructing, and seems to be pushing for me to take over legacy Linux systems work instead. This company is way, way behind the curve, and this guy seems to want to stick me on the old stuff while "his" guys, some of which are less experienced, get all the cool projects working on modernization. It is unlikely that I will ever get to touch AWS at all. That silo is heavily guarded, and I will actually have to hand over control of the AWS accounts from the child company, probably losing my admin access in the process.

So, I am looking to bounce after a few months if something does not change, but I am still going to fully use the company benefits to which I am entitled.

&#x200B;

I already own cantril.io "All the things" AWS bundle and completed a couple of certs from when I was learning on the job for our abandoned cloud app, and I have a few months left on a Redhat Learning Subscription that includes unlimited courses and 5 exams that I will never be able to fully consume. I'll probably use that to continue learning about OpenShift and continue waiting for a opportunity to actually be allowed to work on

containerization with my internal team.

Given the above, for technical or non-technical professional development, how should I spend the company's $1000? I do not have to pay it back if I leave.

Sorry for the rambling.

https://redd.it/12fpjs7
@r_devops

Need to learn AWS and Kubernetes ASAP

I’m a Linux System Admin and I need to learn AWS and Kubernetes ASAP and in the next few months. I have 3-4 hours Mon-Fri and 6-8 hours Sat-Sun available to study. Can someone kindly help me with a good and efficient study path, courses and materials?
For AWS i’m looking to start down the Solutions Architect Associate track

https://redd.it/12fsj4r
@r_devops

Version control table changes with a data warehouse in a multienvironment setup?

When working with traditional databases like MySQL, we can use migration tools such as Python Django Migrations to write down changes to our tables in code. We can then run these changes in our CI/CD pipeline while deploying updates to new environments, thereby applying the changes to the environment's database. Typically, these changelogs are stored in the database itself.

For data warehouses, we could also store the changelog in the database. However, some data warehouses (like BigQuery) do not allow any data mutation within the first 30 minutes of a single row insert. This means that only read operations are allowed, making rollbacks (deleting a record) a difficult and time-consuming process.

Do you have any ideas or solutions for dealing with this issue?

https://redd.it/12fszhd
@r_devops

List of DevOps / Engineering Capabilities

Hello! I want to start a list with all DevOps, SRE and Engineering Capabilities. For example, CI, CD, Test Driven Development, Observability, Feature Flags ... all of that. Has anyone seen a list like this?

What capabilities are trending? What capabilities do you use?

Thanks!

https://redd.it/12fuxy5
@r_devops

How do you deploy ephemeral Windows Server with Terraform on-premise?

I'm trying to deploy Windows Server instances with Terraform on my Proxmox homelab.
Including the whole user setup, partitioning and software installs.
It's the preparation for doing this on VMWare Cloud Director at work... and because there is no VCD provider I sadly can't do it with Hashicorp Packer.

I found CloudBase-Init for doing this in Windows, but I'm not sure if this is the best solution.

The last goal is to do this in KubeVirt - i just now got all the ball rolling for Terraform & Cloud-Init based K8 cluster deployments.

&#x200B;

Did anyone here do this already?
Any tips?


PS: We have legacy software that needs windows as the target system. I want to automate the app & environment deployment for internal testing.

https://redd.it/12fse6m
@r_devops

Finally reading "Heart of Darkness" by Conrad and slowly realizing "The Phoenix Project" is the same story but for Ops/programmers

The similarities are striking and undoubtedly intentional: allusions abound.

To my mind it's the same story:

- Individual is restless (in his office/duties)
- Individual is hired to solve a problem for a Company
- Individual discovers his predecessor was violent (by turns violence in HoD become Arrogance in TPP)
- Individual discovers his new office is cult-like
- Individual begins to dig deeper and discovers the breadth of that cult-mentality which renders his Company incapable of functioning

etc. etc.

Both are basically a re-telling of Plato's Cave too, which is curious to me.

I am only half-way through HoD and lent my copy of TPP to my boss some years ago so the likenesses are only from memory. But the more I read of HoD the more convinced I am that it's a retelling of that story.

What's your opinion on the similarities or discontinuities between the two?

Is all a stagnant Org needs is some semblance of the (independent) perspective? That seems naive in and of itself. idk.

just thinking out loud; please don't admonish me for my first draft of thoughts on this.

https://redd.it/12g6usa
@r_devops

Introducing the Comprehensive DevOps Learning Series


Greetings, r/devops community! I’m excited to announce that I’m starting a "Comprehensive DevOps Learning Series." This series of posts will be designed to provide a thorough and detailed understanding of DevOps concepts, practices, and tools for professionals with various technical backgrounds.

Whether you're just getting started or have experience in the field, this series aims to serve as a reliable resource for advancing your DevOps expertise.

Throughout this learning journey, we will explore the foundations of DevOps, practical implementation techniques, real-world applications, and much more. The series will be structured as follows:

1. Introduction to DevOps: Acquaint yourself with the historical context, underlying principles, advantages, and culture of DevOps.

2. DevOps Practices and Tools: Familiarize yourself with key DevOps tools and techniques, including CI/CD, IAC, and containerization.

3. DevOps Lifecycle: Delve into the DevOps lifecycle and learn how to implement it effectively in your projects.

4. DevOps Methodologies and Frameworks: Understand how to integrate DevOps with Agile, Scrum, Kanban, SRE, and ITIL to achieve better outcomes.

5. DevOps in the Cloud: Examine the integration of cloud platforms such as AWS, Azure, and GCP to optimize your DevOps processes.

6. DevOps Case Studies and Success Stories: Analyze real-world success stories of companies like Netflix, Etsy, Amazon, LinkedIn, and your company too!

7. DevOps Challenges and Solutions: Overcome common obstacles and pitfalls by employing industry best practices and expert insights.

8. DevOps for Small Teams and Startups: Discover how to adapt and scale DevOps principles to suit small teams and startups.

9. DevOps Career and Certification: Enhance your career with insights into job roles, skills, certifications, resume development, and interview preparation.

10. Community and Resources: Identify essential books, blogs, websites, influencers, and conferences to stay informed in the rapidly evolving DevOps landscape.

11. Conclusion/collaboration: Summarize your learning experience and explore future avenues for growth within the DevOps domain.

My goal with this series is to create an engaging, technically focused learning experience where community members can exchange ideas, resources, and insights to foster collective growth. I encourage you to actively participate in the discussions and share your knowledge, resources, challenges, and successes. With this foundation, let's embark on our journey towards a deeper understanding of DevOps principles and practices.

Notes:
Links will be added here to the different posts as I can write them. My current goal is to post weekly, and there’s going to be multiple posts per topic that I’ve outlined above.

https://redd.it/12gcft0
@r_devops

Azure resources like the ones that Adrian Cantrills have for AWS?

Looking to learn more about Azure and I've used Adrians courses and material before for AWS, which are excellent.

Any equivalents for Azure?

https://redd.it/12ge90i
@r_devops

The History and Evolution of DevOps

Series index

Hello, r/devops community! I’ve already prepared the first real post in the series:

As we dive deeper into the Comprehensive DevOps Learning Series, this post will take you through the history and evolution of DevOps. Understanding the origins of DevOps will provide valuable context for grasping its principles, methodologies, and the rationale behind its growing adoption.

The Pre-DevOps Era

Before DevOps emerged as a popular methodology, software development and IT operations were generally treated as separate entities. Developers focused on writing code, while operations teams were responsible for deploying and maintaining the software in production. This division often resulted in bottlenecks and delays, with both teams working in silos and having different goals and priorities.

The Birth of DevOps

The term "DevOps" was first coined in 2009 by Patrick Debois, a Belgian consultant and Agile practitioner, who organized the first "DevOpsDays" conference in Ghent, Belgium. The movement was inspired by the need to break down silos between development and operations teams to improve collaboration, reduce friction, and increase efficiency.

However, the seeds of DevOps were sown earlier, around 2007, with a few pioneering companies exploring ways to address the challenges of an increasingly fast-paced software development and deployment landscape. This shift can be traced back to:

Agile Development: The Agile Manifesto (2001) emphasized collaboration, iterative development, and continuous improvement. Agile principles laid the groundwork for better communication and teamwork between development and operations.

Continuous Integration (CI): CI practices, pioneered by Martin Fowler and Kent Beck, automated the integration of code changes, fostering a culture of collaboration and paving the way for DevOps.

Lean Manufacturing: DevOps also drew inspiration from the Toyota Production System, a precursor to Lean Manufacturing. The focus on minimizing waste, streamlining processes, and incorporating customer feedback resonated with the goals of DevOps.
DevOps Evolution and Adoption


Since its inception, DevOps has evolved significantly, driven by technological advancements and changing organizational needs. Key milestones in its evolution include:

Infrastructure as Code (IaC): The emergence of IaC enabled IT infrastructure to be managed through code, making it versionable, reusable, and reproducible. Tools like Puppet, Chef, and Ansible contributed to IaC's growing popularity.
Containerization: The introduction of containerization technologies like Docker and Kubernetes transformed the way applications are developed, deployed, and managed, making it easier to maintain consistency across environments.

Cloud Computing: The rise of cloud platforms such as AWS, Azure, and GCP provided scalable, flexible, and cost-effective resources that significantly enhanced the potential of DevOps practices.

Microservices Architecture: The transition from monolithic to microservices architecture allowed developers to build, test, and deploy individual components of an application independently, further enhancing the benefits of DevOps.

DevSecOps: The growing importance of security in the software development lifecycle led to the integration of security practices into the DevOps pipeline, giving rise to the concept of DevSecOps.

Site Reliability Engineering (SRE): Google's SRE framework brought a more structured and measurable approach to managing large-scale systems, aligning well with the goals of DevOps.
As more organizations recognized the value of DevOps, its adoption grew, and it became an essential approach for companies aiming to deliver high-quality software quickly and efficiently.

In the upcoming posts, we will delve deeper into the principles, benefits, and culture of DevOps, as well as practical tools

and techniques that have emerged from this evolution.

Share your thoughts on the history of DevOps in the comments below.

https://redd.it/12ge71h
@r_devops

Best study tools to learn azure and azure devops?

Hi guys I need to learn Azure as a whole and Azure Devops as a focus. What courses, youtube videos, or instructors do you recommend? I have my AWS Solutions Architect professional exam, so I have a fair bit of cloud experience, just nothing on azure and need to learn it asap for a new role.

https://redd.it/12gelug
@r_devops

DevOps to Product owner

Hello everyone. I've been struggling over the past few days to decide which path I need to pursue and would appreciate your thoughts. I have 4.2 years of IT experience and 2 years as a DevOps support engineer, and I have been offered two positions: associate software engineer and associate DevOps engineer. I've spent the last 6 months upskilling myself in Terraform, AWS, Kubernetes, Gitlab CICD, and other DevOps tools to become a DevOps engineer but I m not sure if I will love this in the future.

I am now confused about what role to take. If I opt for the Associate DevOps Engineer position, I will only be in the DevOps space, such as Senior DevOps or Cloud Architect. If I opt for the Associate Software Engineer position, I can move later to any role (Senior Software or Product Owner). However, I want to move to a product owner role in the future as I would have better influence on products, but I am not sure which role would be most suited if I decide later to become a Product Owner.

I discussed with a few product owners in my company, and they advised me. It would be tough for DevOps Engineers to transition to product owner compared to Software Engineers as they have more knowledge of product compared to others

https://redd.it/12gj4es
@r_devops

How should I approaching wanting to move to a different team under the same senior director?

I work as a SysAdmin and support engineer for complex system legacy app that is being decoupled into new applications using React UI, Azure, Google Anthos, MySQL, etc. My team was rebranded as "DevOps Support Engineers," which mainly involves running Jenkins jobs, monitoring Kubernetes pods, and Splunk alerts. We contact DevOps engineers or dev leads to fix issues. My daily role is still supporting the legacy app doing SysAdmin tasks, but also incident, problem and change management. My co-workers are a little more involved in the legacy app working with PL/SQL code, etc.

I want to transition to the DevOps team and I'm working on improving my skills in Kubernetes, Terraform, Google Anthos, Azure, and Jenkins (Groovy).

I have a good relationship with our senior director who manages both teams. How should I approach him and/or direct manager about joining the DevOps team?

https://redd.it/12gkeso
@r_devops

Do I really need DevOps?

Hello,

I am managing an automation (RPA) practice in my organization which is in the business of Asset Management.

The automation practice was established in my org two years ago. From then till today, the automation infrastructure (we're on UiPath) is on a single node on-premise setup. In these two years, a lot of business verticals have become highly dependent on automation for every day critical business tasks. Therefore we have come to a conclusion that we need to plan for a high-availability and disaster recovery setup.

We've also taken a call to build it on Azure + on-premise (Hybrid model). Now my question is, should we plan for introducing DevOps into the automation practice? Could this be a use case where DevOps can make an introduction and spread from there?

My primary reason for DevOps is that:

1. We're going to have a complicated infra setup, it will be easier to maintain the environment across DEV/UAT/PROD
2. It will also help us reduce deployment time

Note: My organization does not have DevOps as of now.

https://redd.it/12glare
@r_devops

Hired as an external DevOps engineer with unclear objective - what should I do?

I've been hired as an external DevOps engineer into a project and I don't know how I feel about it. I share my situation here because some opinions of more experienced engineers could be valuable for me and perhaps others are or have been in similar situations and would like to discuss it or learn from it.

# Description of the situation

The project has been built up by three developers over the last three years and is fairly complex. The problem is that all the developers will leave the company in the next 1-3 months. I have been told by my manager that it is is my job now to "conserve the knowledge". It is planned to hire additional developers at a later point, but it is not communicated with me when this is planned and what skillsets these new team members will or should have.

They already have documented a lot of their processes, but without having worked in the team, I feel like it is impossible to know whether what has already been documented is complete or should be extended.

I could go through the documentation and look for things that should be documented or add notes to the existing docs where I believe something is missing. But there is no way for me to ensure that everything will be documented. One person cannot "conserve knowledge" in a couple of months. I could do this after having worked in this project for several months, but not in the short timeframe of 1-3 months.

Another difficulty is that most of the code is written in languages I don't have any experience with, which was communicated before I started. I have experience related to the "DevOps" technologies they use, but apart from that I really feel a bit lost with the existing codebase. Again, they knew from the beginning which technologies I had experience with and which not.

Another point is that I don't feel like I learn so much about the project by reading their documentation and code. The only way to learn what is going on in this project is to actively work on it. So I proposed to work on open tasks while checking documentation to get more familiar with everything. The response was that there are currently no open tasks for my skillset.

This is why I believe my job doesn't really make any sense. One person cannot "conserve knowledge" in a couple of months. This is the job of the developers during development in the form writing documentation and assuring a certain level of quality regarding the documentation. This development process should always see the possibility that people may leave at some point. It cannot be fixed by one person in a few months.

What do you think? Am I right? What should I do now to not end up in a situation that will be very difficult to handle for me?

https://redd.it/12gp2jo
@r_devops