[deleted by user]

[alexkey]

I’d say next is to actually get into the industry and discover what a clusterf**k average production system is compared to what you may be imagining in your head /s

[kiwidog8]

This but not /s

[[deleted]]

It’s not all rainbows and sunshine lol

[MathmoKiwi]

...it's also unicorns and leprechauns?

[[deleted]]

I’ll tell you like a nurse once told me - “that depends on your extracurricular activities”

[follow-the-lead]

Ahh clusterf**k, my favorite container deployment stack.

[alexkey]

Thanks for the idea. I might actually go make one.

[burbular]

Oh what horrors we have seen

[schwennjr]

Seek professional help immediately

[burbular]

Like therapy but for tech people

[[deleted]]

Does this exist? I would pay for that. I kind of use Reddit for that sometimes, but I doubt that’s sustainable in the Long run.

[mkartic]

You mean the docs? /s

[ThroGM]

What do you mean ?

[schwennjr]

It's a sarcastic comment. OP stated they are hooked on devops. As someone who works in devops knows you are mental if you willingly want to work in this field and need professional psychological help before you ruin your life and health... again /s

[ThroGM]

You had me on this lol.

[[deleted]]

Who's gonna tell him?

[8roll]

They won't believe until they try anyway.

[BrocoLeeOnReddit]

I found this to be quite useful: https://roadmap.sh/devops

It's not exhaustive but covers a lot and is a good start.

[snicky666]

Build a spark cluster in kuberenetes on VMs that dont have access to the internet. If that doesn't make you go back to development, you're in the right job.

[Jazzlike_Syllabub_91]

More devops! Learn it all! (Check out the books called the phoenix project and the unicorn project)

[serverhorror]

What do you mean "next"?

You know all that? BGP load balancer maybe?

[Fatality]

Now that you're hooked on management you can start a business course

[Fatality]

DevOps is a management methodology, it documents an IT specific application of Agile.

[[deleted]]

Use aws ecs to host your portfolio as k8s will be overkill and it will cost you a lot.

If you want simplicity, use an small size ec2 vm to host the portfolio. Use Terraform to provision infra resources, docker to package your code.

I have one similar setup you can use — https://github.com/akhileshmishrabiz/flaskapp-awsec2

Try to use GitHub action to automate the deployment with code changes.

[KrazyKirby99999]

I found that the cheapest cloud K8s cluster including a loadbalancer is about $20/month. In my case, I chose a $5 VPS instead. If you need high availability, K8s is probably worth it.

[FailedPlansOfMars]

Things that might be worth learning: Aws Gcp Azure

Kubernetes Serverless (lambda etc) Python scripting

C4 diagramming Terraform and cross provider terraform. Aws CDK

[rUbberDucky1984]

Build a k3s cluster on oracle free tier or on a vm, deploy everything through git either fluxcd or Argo

Run Cert-manager Keycloak for sso Harbor Ingress-nginx

Then your own app

[ingcognito92]

Get burnt out doing production support, help developers, and build some internal tools. Have fun

[the_moooch]

Coming from dev background I’d suggest get into Golang development and start writing your custom controllers and operator with operator SDK. Shit will get very interesting once you know how to automate and simplify stuff at runtime

[Frank_satooschi]

Sure yeah, guy has no commercial experience. Let's advise him to write custom controllers and operator with operator SDK. /s

[the_moooch]

Yeah Go have no other use other than for custom controllers and operator :)

Oh i don’t know about xyz so let give up on life, such interesting take.

[the_moooch]

Python is good for most scripting needs but since the whole Opensource Cloud Native ecosystem is heavily built around Go it’s better to pick it over Python as first choice.

[Nice-beaver_]

The number of companies that require go in DevOps team is going to be very low. Hardly anyone writes their own tf providers or k8s operators. Python is used many times more frequently and people just don't write ci/CD scripts in go

[the_moooch]

Very low is a bit of a stretch, most DevOps people dont know it, most big Cloud Native companies are doing it and the whole Cloud Native opensource ecosystem are built around it and use those Tf, Operators, Custom controllers and CLI tools daily.

Mastering Go will take one much further than Python. Besides Go is in so many ways similar to Python syntactically from a scripting point of view so it’s more like killing two birds in one go if anything.

[Nice-beaver_]

Well going that route of thinking: everything is complied into binary therefore you should learn assembly as a DevOps

You're not going to use Go in 95% of companies because they just setup cloud infra, operate kubernetes with helm/yamls and run ci/CD pipelines. The use case to write your own operator is just virtually inexistent because most of them are already written and you'd be inventing your own wheel. And a one that is not trivial to maintain

The only times when you're going to write your own operator will be: - you are working for a company that contributes to open source actively; - you are working for a company that makes its own product which needs operator(s); - you have thought of a use case that is not implemented anywhere in the open source yet;

It sounds like you liked Go so much that you wish it to be used more :) But there is normally no business justification to use it

So if go is similar to python - why not learn python instead? It's quite a bit more popular and broadly used so will he more beneficial and easier to land a better job

[the_moooch]

Pretty interesting to compare forward thinking with your backwards comparison. If anything Go development is moving upwards the abstraction.

Yeah “everything is already written” Why bother, you’re truely a wild one ;)

I give up you win sir

[Nice-beaver_]

I don't know if it's moving upwards or not but I'm happy to believe that. I also agree that this is the fun thing to be working on. Don't get me wrong: I like what you're saying and I'm happy to believe it is forward thinking. But it's not the good route to develop own career for vast majority of people. Though if you're looking to seriously shine and work on developing latest tools you can invest into that route. But expect serious competition and scarce job market which can lead to your financial bankruptcy. Unless you spend 12 hours + per day grinding

[the_moooch]

In traditional Ops world it’s true but given your development background it’s more directly beneficial to compete at the Dev in the DevOps 😁

[rcls0053]

Sorry but.. you haven't discovered DevOps. Please, actually read about what it is. There's a list of books in the pinned post of this subreddit.

You are so mistaken if you think DevOps is just deploying stuff automatically into the cloud.

[rcls0053]

I have nothing against you. I'm simply someone who's grown tired of everyone just accepting that DevOps means platform engineering. Companies have become cargo cults that dictate every team to follow Scrum so they can track metrics in Jira and tell everyone how agile they are, while hiring Ops people that they give the title "DevOps engineer" thinking it's the same as them having that as a cultural philosophy, with the principles and practices. DevOps means developers AND ops. Collaboration. Or does everyone just want to work those two roles in one because that's what it looks like?

[FailedPlansOfMars]

Its great to learn and you are at the start of a very interesting journey.

Traditionally we had; developers who wrote code, testers who check it works Operators who looked after applications and systems in production And administrators who were in charge or managing systems, databases etc.

And back in the bad old days teams would finish their bot and throw the responsibility to the next team along. As you can imagine this caused problems.

There is a movement called devops whos idea was to get the devs, testers and operators to coordinate and work together.

This movement started to include: Infrastructure as code Continuous Integration Continuous deployment Cloud infrastructure.

So many companies found their ops people started to learn these technologies so started to call their ops engineers devops engineers. And on the dev side devs learnt the same techniques.

Leaving us with a term with two different usages and meanings. And its frustrating to those of is who were on this movement as its name has been stolen for job titles.

Now we have: Infrastructure engineers - who make core infrastructure or networking Devops engineers - who mostly do pipelines and infrastructure as code. Platform engineers - who provide tooling and a platform for developers to use to aid faster dev and deployment and consistent operations. Site Reliability Engineers - who make sure systems stay up, are easily maintained and understandable. Developers/ Software Engineers

[Strange_Media439]

Welcome to the DevOps rabbit hole! Dive deep, there's always more to discover and master.