Learning tutorial
A case of container landing practice
With the continuous development of the company’s business and the transformation of micro-service, there are more and more projects and more and more daily releases. The traditional operation and maintenance system is inefficient and difficult to meet the needs of the business. In recent years, Docker has developed rapidly. The concept of building once and running everywhere has also brought a glimmer of hope to operation and maintenance. The emergence of Kubernetes platform has accelerated the implementation of containerization in enterprises. This article mainly shares Kubernetes in a landing practice case.
DockOne.io
Explain the distributed coordination service ZooKeeper
In this article, we briefly introduced Chubby, Google’s distributed lock service, and ZooKeeper, which also provides distributed lock services.
Personal blog
Kubernetes Container cloud practices
With the progress of society and the development of technology, people have a more urgent demand for the efficient use of resources. In recent years, with the rapid development and maturity of the Internet and mobile Internet, the micro-servitization of large applications has also attracted the enthusiastic attention of large enterprises, and the container cloud solution based on Kubernetes+Docker has also entered the public’s vision. Kepler Cloud is a microservice governance solution based on Kubernetes+Docker+Istio.
Appropriate technology a long time
Flannel for Kubernetes network Analysis
Flannel supports multiple network modes, including VXLAN, UDP, HOSTGW, IPIP, GCE and Ali Cloud. The difference between VXLAN and UDP is that VXLAN is a kernel packet, while UDP is a Flanneld user-mode program packet, so the performance of UDP is lower. Hostgw mode is a host gateway mode. The gateway of a container to another host is set as the network card address of the host. This is very similar to Calico, except that CalICO is declared through BGP, while HostGW is distributed through etCD in the center, so HostGW is directly connected. Overlay packet sealing and unpacking are not required, so the performance is relatively high. However, the biggest disadvantage of hostGW mode is that it must be in a Layer 2 network. After all, the next hop route must be in the neighbor table, otherwise it cannot be passed.
Creditease Institute of Technology
To traditional enterprise friends: not enough pain micro service, pit!
At that time, I thought that since microservice is to transform applications, do microservice governance, such as registration, discovery, fusing, limiting, downgrade, etc., of course, I should start from the application development team. Generally, I would have fun at the beginning of the conversation, from single architecture, TO SOA, to microservice architecture, from Dubbo to SpringCloud. However, it will inevitably involve the release and operation of microservices, DevOps and container layer, which are not under the control of the development team. Once the o&M team is involved, the acceptance of containers becomes a problem, the difference between traditional physical machines and virtual machines, what risks will be brought, etc., etc. The fact that containers are definitely not lightweight virtualization, in particular, is not immediately clear. What’s more, even if it is clear that there are online application containers, once something goes wrong, the problem of who is responsible for the container will often lead to the blurring of the boundary between the application layer and the infrastructure layer, which makes both sides of the responsibility will hesitate.
Liu Chao’s popular cloud computing
Four common Kubernetes monitoring traps to avoid
For the current Kubernetes monitoring approach, due to the lack of end-to-end visibility and error prone migration, there are shortcomings. Here are four common challenges we might encounter when monitoring Kubernetes and suggestions for how to solve them.
The New Stack
An exploration of data stored in Kubernetes component ETCD
ETCD is in the K8S stack what databases (Mysql, Postgresql, Oracle, etc.) are in Web applications, storing all the metadata in a K8S cluster (in a key-value manner). So the real question is: how is this metadata organized and stored? This paper explores this problem.
Personal blog