Operations
Adding imagePullSecrets to Kubernetes
· β˜• 2 min read
1. Adding via kubectl create 1 kubectl create secret docker-registry mypullsecret --docker-server=harbor.chenshaowen.com --docker-username=robot-test --docker-password=xxxxxx With kubectl create you can add credentials for pulling images directly. 2. Adding via ~/.docker/config.json Log in to the image registry with an account and password 1 docker login harbor.chenshaowen.com:5000 1 docker login harbor.chenshaowen.com You can add more than one.

Problems Using the obsutil Command in Containers
· β˜• 1 min read
1. The container’s ulimit is set too low Error message: 1 2 3 4 5 6 7 CheckpointDir: /root/.obsutil_checkpoint OutputDir: /root/.obsutil_output runtime: mlock of signal stack failed: 12 runtime: increase the mlock limit (ulimit -l) or runtime: update your kernel to 5.3.15+, 5.4.2+, or 5.5+ fatal error: mlock failed Under Docker, you can add the ulimit parameter at startup 1 docker run -it --ulimit memlock=-1 .

An Advanced User Guide to Thanos
· β˜• 5 min read
1. Aggregating Data with Query As shown above, the components that Thanos Query can connect to are: Thanos Store Gateway Thanos Query Thanos Receive Prometheus, by way of Sidecar By cascading Thanos Queries, we can perform correlated queries across components and build an extremely large monitoring system. This also means that every connected component should provide a sufficiently fast Prometheus API.

A Global Image Distribution Network
· β˜• 7 min read
1. Global Network Planning Many global, multi-region infrastructures do not put much thought into network planning at the outset. Once the business grows complex enough, they are forced into network adjustments and optimization. Yet any major network change has a huge impact on the business. In the end you are stuck in a dilemma, able to do nothing but invest more people, carry the baggage of history, and walk along the edge of a cliff again and again.

Managing Data from Multiple Prometheus Instances Centrally with Thanos
· β˜• 10 min read
1. Layering of Monitoring As shown above, when building a monitoring system, two strategies are used: Layered monitoring. The benefit of separating IaaS, MySQL middleware, and App layer monitoring is that the systems have high availability and fault tolerance between them. When App layer monitoring stops working, IaaS layer monitoring will immediately make that visible.