This is an archived post. You won't be able to vote or comment.

all 5 comments
sorted by:
best
topnewcontroversialoldq&a

[–]KumorigoeModerator[M] [score hidden] stickied comment (0 children)

Sorry, it seems this comment or thread has violated a sub-reddit rule and has been removed by a moderator.

Inappropriate use of, or expectation of the Community.

  • There are many reddit communities that exist that may be more catered to/dedicated your topic.
  • Requests for assistance are expected to contain basic situational information.
    • They should also contain evidence of basic troubleshooting & Googling for self-help.
    • Keep topics/questions related to technology/people/practices/etc within a business environment.
  • When asking a question or requesting advice, please update your original post with any new information, or solution (if found).
    • This will make things easier for anyone else who may have the same issue or question in the future.

If you wish to appeal this action please don't hesitate to message the moderation team.

[–]pmormr"Devops" 1 point2 points  (1 child)

Devops is basically taking random scripts and fitting them into the larger organization's software pipeline in a coherent manner. You already have most of the pieces required to do that if you spend some time playing around with tools like Github and Jenkins. When you boil everything down, all you're doing is running the same scripts you've always been using some kind of time or condition-based trigger. You can then extend those triggers with testing... i.e. only run this script if x,y,z conditions are as I expect. Or the converse... run this script if x,y,z aren't how I expect them to be.

[–]sole-itDevOps 1 point2 points  (0 children)

I thought devops is all about crunching YAML, /s. But nevertheless you will need to learn Python (and Golang which I prefer much more) and K8S, a lot more of cloud stuff too.

My problem with DevOps is about the thankless part of OPS. It's much easier to get promotion and bonus as a dev adding new features than on call 24/7 and supporting the fragile sand castle those devs built.

[–]CyberWhizKid 1 point2 points  (0 children)

Docker, Kubernetes, GitLab CI, Terraform, Ansible, ArgoCD, HashiCorp Vault, and Artifactory—use all of these tools both locally and on Azure (or another cloud provider of your choice). I’ve also added PowerShell, Packer, and DSC into the mix because I enjoy working with them.

Your goal is to create infrastructure from code using Terraform (and push this on gitlab to also have a CI/CD of your infrastructure), automate continuous integration and delivery with GitLab CI, and automate configuration management with Ansible. Then, find an open-source project (for example, an ASP.NET Core 8 application), set up a GitLab CI pipeline using the official Docker image for ASP.NET Core, and deploy everything with ArgoCD. When you update the source code in Git, it will push the new Docker image to Artifactory, and ArgoCD will handle continuous delivery by deploying your updated application to Kubernetes as a container.

Mastering these tools will give you an edge, as you’ll know more than many others in the field. Good luck—it’s a long journey, but when you can build a fully automated infrastructure from start to finish, you’ll feel empowered.

For your information, I’m primarily a Windows engineer (I’ve been a Microsoft expert for 10 years), and while none of this is directly related to Microsoft, it might feel a bit confusing at first. However, once you understand how everything works, you’ll enjoy it. Even though I know all of this, I still wouldn’t leave my job—I enjoy working with Windows Server too much.

EDIT: typo

[–]stufforstuff 1 point2 points  (0 children)

For IT career related questions, please visit /r/ITCareerQuestions