On the "Golden Nine Silver Ten", young graduates are full of hope and anxiety, looking for and competing for a job opportunity. The development students who are already on the job also want to get better treatment and a bigger platform through social recruitment or internal promotion.
However, there are a large number of interviewers, and the technical market is relatively cold. The students who are interviewed have to face the huge competition of N candidates for 1 position.
Q: Under this situation, how can we get more and better offers?
A: Short-term preparation - brushing interview questions; long-term planning - consolidating core skills.
How to brush the interview questions? Brush high-frequency questions, deep questions, and time-sensitive questions.
How to consolidate core skills? First in-depth understanding of the principle, and then systematically apply it to practice.
In the past two years, Kubernetes has defeated Swarm and Mesos and has almost become the de facto standard for container orchestration. BAT, Didi, JD.com, Toutiao and other major manufacturers are all vying to focus on containers and K8S projects, trying to "catch big fish with a long-term approach". ".
**Let's talk about Ali. At present, basically all businesses are running on the cloud, and half of them have been migrated to their own customized Kubernetes clusters. **It is said that 100% business deployment based on K8S cluster is planned to be completed this year. In terms of service mesh, some departments of Alibaba (such as Ant Financial) already have online businesses in use.
This fully illustrates the status of containers in today's software R&D field. Therefore, mastering container technology has become an important option for many companies when recruiting.
However, container technology itself is biased towards operation and maintenance, and concepts such as namespace resource isolation and cgroups resource limitation are difficult for developers to understand. In the past two years, when discussing the implementation of K8S with friends, some issues have been repeatedly mentioned, such as:
- Why can only "one process" run in a container?
- Why is a JVM parameter that has been used before, not working in the container?
- Why can't Kubernetes fix IP addresses? The container network cannot be connected, how to debug?
- What is the difference between StatefulSet and Operator in K8S? How should PV and PVC be used?
**The answers and principles of these questions are not complicated, but it is difficult to explain them clearly in one or two sentences. **Because container technology involves knowledge of operating systems, networks, storage, scheduling, distributed principles, etc., it is a veritable full-stack technology.
However, the main lines in its technical system that "involve the whole body", such as the importance of the Linux process model to the container itself, and the role of the "controller" model in guiding the entire K8S project outline, etc., will not be shown in detail in Docker or Docker. Kubernetes official documents, but they are the essence of mastering the container technology system .
To be honest, I have read a lot of K8S materials in recent years, but there are not many really systematic ones, so I will share my carefully collected ** " Kubernetes from Theory to Practical Learning Manual" from entry to soul, this note It was written by Ali and only circulated internally. After several twists and turns, I finally got it. I have read the small part, and it is really good to share it here and give back to my friends. What exactly was written in this note? Let's take a look **
Kubernetes from theory to practical learning manual directory and content display
Chapter 1: Getting Started with the Basics
- Introduction to Kubernetes
- Basic Concepts of Kubernetes
- Kubernetes 101
- Kubernetes 201
- Kubernetes cluster
Chapter 2: Core Principles
Introduce the Kubernetes architecture and core components, including:
- core principle
- Architecture Principles
- design concept
- core components
- resource object
Chapter 3: Deployment Configuration
This chapter describes how to deploy the created Kubernetes cluster, how to install the kubectl client, and the recommended configuration. Among them, Kubernetes-The-Hard-Way introduces the detailed steps to deploy a Kubernetes high-availability cluster step by step in the Ubuntu virtual machine of GCE. These steps are also applicable to other systems such as CentOS and other public cloud platforms such as AWS and Azure. The main contents are as follows:
- Deployment Guide
- kubectl install
- Stand-alone deployment
- Feature switch
- best configuration
- Version support
- Cluster deployment
- Add-ons
- Kubernetes-The-Hard-Way
Chapter 4: Plugin Extensions
The architecture of Kubernetes is very flexible, providing a series of extension mechanisms from API, authentication and authorization, admission control, network, storage, runtime, and cloud platform, etc., to facilitate users to expand the functions of the cluster without intrusion. The main contents are as follows:
- API extension
- Access control
- Scheduler extension
- network plugin
- Runtime Plugin CRI
- storage plugin
- network policy
- lngress Controller
- Cloud Provider extension
- Device plugin
Chapter 5: Service Governance
This chapter introduces Kubernetes service governance, including container application management, service mesh, and operators.
Chapter 6: Practical Cases
Kubernetes practices and common tips, including
- resource control
- monitor
- log
- High availability
- debugging
- Port Mapping
- port forwarding
- GPU
- Safety
- audit
- Backup recovery
- Certificate rotation
- large-scale clusters
Chapter 7: Troubleshooting Guide
Kubernetes clusters and general methods for application troubleshooting, including
- Troubleshooting abnormal cluster status
- Troubleshooting Pod Running Abnormal
- Network exception troubleshooting
- Troubleshooting persistent storage exceptions
- Windows Container Troubleshooting
- Troubleshooting cloud platform exceptions
- Common troubleshooting tools
Summarize
At the moment, you and I may have missed the era of the Internet technology explosion, nor a share of the early digital currency craze. But at this moment, in the field of cloud computing and infrastructure that has been silent for many years, the first historical change in the name of "container" is about to emerge. This time, what reason do we have to sit on the sidelines?