Kubernetes
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.

Using Falco to Monitor Runtime Security
· β˜• 5 min read
1. What Falco Is Falco is a cloud-native runtime security project contributed to the CNCF by Sysdig. Falco implements an extensible event rule filtering engine. Through a series of operations β€” capturing events, matching security rules, and producing alert notifications β€” it can surface security problems in a system. The events come from system calls, and it also supports an ebpf probe; the rules are open source [1] and you can define your own extensions [2].

Using In-Cluster Prometheus to Collect Etcd Metrics
· β˜• 2 min read
1. Skipping Certificate Verification Prevents Scraping If you can skip TLS authentication when scraping metrics, that is the easiest path. The Prometheus ConfigMap configuration looks like this: 1 2 3 4 5 6 7 8 9 - job_name: etcd metrics_path: /metrics scheme: https tls_config: insecure_skip_verify: true static_configs: - targets: ["1.1.1.1:2379"] - targets: ["2.

How to Add Basic Authentication to a Kubernetes Service
· β˜• 2 min read
1. Deploy the Ingress Controller Check the Kubernetes version 1 2 3 4 kubectl version --short Client Version: v1.21.4 Server Version: v1.21.4 Find a compatible Nginx Ingress version Helm Chart version Highest available Helm Chart version Compatible K8s version 3.x.x 3.36.0 1.16+ 4.x.x 4.4.2 1.19+ Reference: https://github.com/kubernetes/ingress-nginx Install the Nginx Ingress Controller 1 2 3 helm upgrade --install ingress-nginx ingress-nginx \ --repo https://kubernetes.