I recommend Devs who want to learn Ops should learn to use infrastructure as code tools, like Ansible for config mgmt and HashiCorp Terraform for provisioning workflow (many devs already are using TF from a self-service module template standpoint).
Then for networking, service mesh seems to be what's making it more dev-approachable these days. For that you should check out HashiCorp Consul, Istio, or Linkerd.
And of course there's Kubernetes, but that's got quite a learning curve. I think a simpler container orchestrator to start with would be HashiCorp's Nomad.
I intentionally avoided to give specific tool suggestions, but since you did:
Great tips!
Just don't go to service mesh 'because it makes networking more dev approachable', ideally you should have a good reason to mess with it, and there are a lot of people just going cause it's trending.
Same for kubernetes some times. That's why I said to look for tools that your company already uses, and expand from there.
I did not give any references about CI/CD, orchestration, and other important Ops/DevOps topics since they so closely relate to tools... But we could give more tips like that here in the comments!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I recommend Devs who want to learn Ops should learn to use infrastructure as code tools, like Ansible for config mgmt and HashiCorp Terraform for provisioning workflow (many devs already are using TF from a self-service module template standpoint).
Then for networking, service mesh seems to be what's making it more dev-approachable these days. For that you should check out HashiCorp Consul, Istio, or Linkerd.
And of course there's Kubernetes, but that's got quite a learning curve. I think a simpler container orchestrator to start with would be HashiCorp's Nomad.
I intentionally avoided to give specific tool suggestions, but since you did:
Great tips!
Just don't go to service mesh 'because it makes networking more dev approachable', ideally you should have a good reason to mess with it, and there are a lot of people just going cause it's trending.
Same for kubernetes some times. That's why I said to look for tools that your company already uses, and expand from there.
I did not give any references about CI/CD, orchestration, and other important Ops/DevOps topics since they so closely relate to tools... But we could give more tips like that here in the comments!