Operations
Dynamic Proxy Envoy
· β˜• 2 min read
Envoy is the third project to graduate from the CNCF, and thanks to features like dynamic configuration and high performance it has become the de facto data plane standard in cloud native. Many projects rely on Envoy to handle data plane traffic while focusing their own efforts on adapting the control plane to their application scenarios, writing user input into Envoy over the xDS protocol.

Network Performance Testing Tool iperf
· β˜• 4 min read
1. Installation Ubuntu 1 apt-get install -y iperf3 CentOS 1 yum install -y iperf3 2. Parameters The principle behind iperf3 is that the client sends packets to the server so the network can be analyzed. It has two running modes: client and server. The iperf3 parameters fall into three groups: common parameters, client parameters, and server parameters.

Several Ways to Inject a Sidecar in Istio
· β˜• 2 min read
The template Istio uses to inject a Sidecar lives in the istio-sidecar-injector ConfigMap. Annotations let you customize the Sidecar’s various parameters, such as CPU usage, proxyImage, and so on. What follows is mainly a summary of the Sidecar injection methods. 1. Add a label to a namespace -> takes effect for the whole namespace Inject the label 1 kubectl label namespace default istio-injection=enabled --overwrite After the application restarts, the Sidecar container will be injected automatically.

Several Traffic Configuration Paths Under an Istio Gateway
· β˜• 2 min read
1. Common Object Configuration 1.1 Gateway selector Selects the Envoy on which the rules take effect servers The domains to match Port Protocol TLS certificate 1.2 VirtualService gateways Specifies the gateway on which this takes effect; the default value mesh is for east-west traffic, while specifying a Gateway object makes it north-south traffic http Layer 7 routing Redirect Rewrite Retry Condition rules Timeout Fault injection CORS policy tcp Layer 7 routing tls Routing with certificates TLS certificate 1.

Optimizing Tekton's Slow Clone Task, Saving About 30 Seconds
· β˜• 13 min read
1. Symptom - Tekton’s Clone Task Is Slow When running the clone task, Tekton is very time-consuming; with multiple repositories it generally takes around 2 minutes 30 seconds. As shown below: A pipeline that only clones takes 2 minutes 16 seconds to run, while the clone script itself actually runs for only 1-3 seconds.