Talk about Kubernetes

Kubernetes 和 Istio

With the continuous penetration of the concept of microservices, more and more companies and developers are trying to turn the previous monolithic services to microservice architecture. ContainerThe emergence of container technology has greatly accelerated this process. Containers and microservices are simply a perfect combination. ,match made in heaven. Because it effectively solves the problem of Nrapid delivery and rapid deployment of multiple services.

However, with the increasing number of services, many companies can hope to combine related services 聚合for efficient deployment and management, so the 服务编排concept appears later . Among the many 服务编排tools, Kubernetestake it in Google的沉淀and 先进的思想turned out to dominate the container field layout, a lot of people are directly look silly .... As a result, a group of start-up companies specialized in Kuberntesmanagement projects, and even domestic leaders Rancheralso updated the 2.0version, focusing on Kubernetesmanagement and upper-level services. Because I really can't do it, in Da Liu's words, this is it 降维打击.

Later, again with the breakdown service module, increasing the number of services, operation and maintenance services is bound to become a problem to be solved, then Istioappeared, with Gooleand IBMthe manufacturers Buff, the service sector has become a shining star of governance , ItsioBased on the idea of ​​separating the data plane and the control plane, allowing effective management of service control strategies.

Architecture development	solved problem
Microservice	Solve the problem of high cohesion and bloated service
Container	Solve the problems of unification, delivery and deployment of the operating environment
Kubernetes	Solve the problem of effective "aggregation" and deployment between services
Istio	Solve a series of governance problems faced by service launches

Kubernetes and Docker do private cloud

2018When I was 20 years old, I felt that using the principle of Kuberntesthinking and adding Docker, I felt that it shouldn't be a problem at all to be a private cloud, or even a public cloud. This idea has been confirmed today.

Kubernetesthought

• Immutable infrastructure Take
  advantage Dockerof the immutability of mirroring; if the container is abnormal, it is no longer like traditional sshdebugging, but directly killdrop the current container and restart!
• Infrastructure is code.
  Management infrastructure is like managing code. Every infrastructure is descriptive; for example Kubernetes, the node、serviceconcept of "in".
• Programmable infrastructure is
  oriented to Kubernetesprogramming and APImanages Kubernetesthe resources in a call mode .

Dockerin principle

• Build once, Run anywhere
  Build once, run anywhere
• All in one
  A containerrun only one application
• Application-centric
  management of the application life cycle elegantly
• Hierarchical governance
  From iaas--> paas--> saas, hierarchical governance, each layer calls each other through interfaces without intruding each other

Speaking of playing these, is it really so smooth sailing, no problem? No, I think Kubernetesthere is another problem to be solved on the above-troubleshooting.

Now the threshold for troubleshooting will be relatively high, and it is not yet simple and easy to use!