2022 Devops roadmap ｜ medium

 【  Source of the article  】https://faun.pub/devops-roadmap-2022-340934d360f9

DevOps  Skills are in great demand , And we need to keep learning and keep ourselves in step with the market demand . This article is to share notes that can help you .

Fundamentally powerful network technology

understand  HTTP/2、QUIC  or  HTTP3、 The first  4  Tier and tier  7  Layer protocol 、mTLS、 agent 、DNS、BGP  And so on , How load balancing works 、IP  surface 、Internet  How it works 、IP  Address and Scheme , Finally, network design .

Master the basic knowledge of operating system , In especial  Linux

Because most systems （VM、 Container, etc ） run  Linux, So it's important to understand this from top to bottom . Learning scheduling 、systemd  Interface 、init  System 、cgroups  And the namespace 、 performance tuning , And master the command line utility  — awk、sed、jq、yq、curl、ssh、openssl  etc. .

CI/CD

If you still like Jenkins , That would be great . however , The world has turned to cloud native pipelines . conceptually , This space has not changed much , But you can see  Github Actions、Tekton  etc. . How to better publish ？ Understand various deployment strategies , Such as blue-green and canary .

Containerization and virtualization

Except for the popular  Docker  Runtime , Try  containerd、podman  And learn how to container applications 、 How to achieve

Container safety

、 How to be in  Kubernetes  Running and orchestration in  VM, see also  KubeVirt  project .

Container arrangement

Kubernetes  Now is the de facto standard for running containers . There is a lot of learning on the Internet Kubernetes The content of . Focus on configuration best practices 、 Application design 、 Security and scheduling . Setting up a cluster is now trivial , But the next day's operational problems , For example setting 、 monitor 、 logging 、CI/CD、 How to expand a cluster 、 Cost optimization and security are some of the questions people might expect you to ask .

Large scale observability

Most engineers know  Prometheus Grafana  Stack or similar stack . The trend shows that , From a performance and cost perspective , Many organizations are integrating their  Kubernetes  Clustering and observability , It helps . understand  Prometheus  Advanced configuration and Architecture , And how to extend them . Research  Thanos、Cortex、VictoriaMetrics、Datadog  and  Loki  Technology . Continuous analysis tools , for example  Parca、 Periscope 、 Super tracking and distributed tracking with open telemetry . Such as  Istio  Such service grids are a popular component of cloud native recipes .

The platform team acts as a product team

The function of the platform team is more and more like a centralized product team , Focus on their internal platform customers , Such as developers and testers . The goal is to improve the way we work and bring some order to the team . Try to improvise developers and  QA  Problems faced by the team . You are the driver of other teams , Instead of doing all the work in a central team , Instead, it instructs the development team to undertake the typical  DevOps  duty . So you can scale up and not burn yourself too much .

Security

In many small organizations , Safety is a second-class citizen . Product functions are given more priority . however , Due to more and more complex attacks and various strict compliance requirements , The company is adapting to the left shift security policy . End to end encryption 、 Powerful  RBAC、IAM  Strategy 、 Governance and auditing 、NIST、CIS、ISO27001  The implementation of such benchmarks is common . Container safety 、 Strategy is code 、 Cloud governance and supply chain security are hot topics .

Programming

DevOps  or  SRE  Roles are now considering developers' cross domain concerns , And create tools that help to improve productivity while implementing standards . Making high-quality platform components requires good software engineering practice and skills .

I can't put enough pressure on this . Excellent organizations are looking for platform engineers with good programming experience . This is also very important in site Reliability Engineering , You need to be proficient in programming , Be able to read 、 Understand and debug code written by others , And repair it if necessary .

Python  and  Golang  It's the most popular . My advice is  Golang, Because it has strong concurrency 、 Strict type checking 、 Adoption in various organizations 、 Tool chains and many major projects are used  Golang  Build features , So by  Python  Learning is meaningful .

You can try some simple things ：

• Write in your programming language  CLI.

• Learn to write  REST API  And interact with the database

• Parallelism and concurrency

Infrastructure is code

Terraform  Is the standard in the project . Once you understand the concept , It's easy to adapt to any other tool , Because most of them are based on  DSL  Of .

cloud

Most clouds work the same way . therefore , If you are familiar with a cloud , You can easily work with other cloud providers . Focus on how to be highly available 、 elastic 、 Design applications using cloud native components in a safe and cost-effective way .

Technical writing

You may wonder why I'm talking about  DevOps  Talk about technical writing . Many people don't pay enough attention to this , But this is very important for how you communicate and cooperate with other teams . The future of work is remote , E-mail 、 Idleness / The team 、 Chat is the main channel to talk to others and convey ideas .

You may periodically create something like an operation manual 、 Post analysis 、RFC、 Documents such as architecture decision records and software design documents . A clear 、 Easy to understand documents can do wonders . It can help you save time for yourself and your readers and improve overall productivity . I suggest you read

This article

.

Field reliability engineering

DevOps  and  SRE  The line between them is getting narrower . In some organizations , The same person may play both roles at the same time . understand  SLI、SLO  And wrong budgets and  SRE  The concept behind practice . Every organization does things differently , So I don't recommend copying and pasting other people's culture into your team . Reference resources

Google SRE  Culture

.

Conclusion

Personally , I am very happy to follow you this year . This is not a definitive list , Because it will change over time .

• Service Grid ——Istio、Cilium Sidecarless  grid 、Tetrate  and  Solo  Of  Gloo  Grid products .

• How to improve developer productivity ？ It's culture 、 A mixture of automation and tools .

• SRE  platform —— cellular ,Last9.

• DevPortals—— Again, it is related to the motivation to improve productivity and bridge the knowledge gap .

• Observability —— Such as open telemetry 、 Hyper tracking 、 Thanos 、VictoriaMetrics、Vector Technology .

• Security —— Supply chain security 、 code signing 、 Strengthen cloud security .

• Golang—— Improve current skills .

• Server free computing and event driven architecture

• Web3 —  Understand and  DevOps  Infrastructure related environment

Keep curious and keep learning . It's easy to keep learning in one bite size , You can work full-time while . If you still have any questions , Please feel free to make an appointment with me . I'd be happy to help .