Cilium的网络加速秘诀同用户态程序交互, 最终实现内核数据进行修改,或者影响内核处 理请求的结果,或者改变内核处理请求的流程。 极大提升了内核处理事件的效率。 截止 linux 5.14 版本,eBPF 有32种类型程序。而 cilium 主要使用了如下类型程序: • sched_cls 。cilium在内核 TC 处实现数据包转发、负载均衡、过滤 • xdp 。cilium在内核 XDP 处实现数据包的转发、负载均衡、过滤 • cgroup_sock_addr policy过 滤,不足: • 一条过滤规则可能需要记录诸 多的CIDR • endpoint身份和 IP 地址耦合, 如 pod 重启后 IP 发生变化, 整集群可能需要同步 信息,刷 新 OVS 流表或者 ipset 规则 • 大规模的 policy ,会一定程度 的影响规则查询的效率,会一 定程度的影响规则更新的时间, 这些都会引入的TPS波动 Cilium policy采用了 identity0 码力 | 14 页 | 11.97 MB | 1 年前3
Cilium v1.5 DocumentationFunc�onality Overview Ge�ng Started Guides Installa�on Security Tutorials Advanced Networking Opera�ons Is�o Other Orchestrators Concepts Component Overview Assurances Terminology Address Management Mul� Host Requirements Configura�on Network Policy Endpoint CRD Kubernetes Compa�bility Troubleshoo�ng Is�o Ge�ng Started Using Is�o Docker Cilium with Docker & libnetwork Mesos Cilium with Mesos/Marathon Envoy Envoy Go Cilium? The development of modern datacenter applica�ons has shi�ed to a service- oriented architecture o�en referred to as microservices, wherein a large applica�on is split into small independent services0 码力 | 740 页 | 12.52 MB | 1 年前3
Cilium v1.10 Documentationconnectivity to resources outside the cluster (e.g., VMs in the VPC or AWS managed services) is masqueraded (i.e., SNAT) by Cilium to use the VPC IP address of the Kubernetes worker node. Excluding the lines for connectivity provided by Cilium and NetworkPolicy applies to them: $ kubectl get pods --all-namespaces -o custom- columns=NAMESPACE:.metadata.namespace,NAME:.metadata.name,HOSTNETWORK:. spec.hostNetwork --no-headers=true the installation, please refer to the Troubleshooting section and / or seek help on Slack. When do I need to use a kvstore? Unlike the section Quick Installation, this guide explains how to configure0 码力 | 1307 页 | 19.26 MB | 1 年前3
Cilium v1.11 Documentationconnectivity to resources outside the cluster (e.g., VMs in the VPC or AWS managed services) is masqueraded (i.e., SNAT) by Cilium to use the VPC IP address of the Kubernetes worker node. To set up Cilium overlay connectivity provided by Cilium and NetworkPolicy applies to them: $ kubectl get pods --all-namespaces -o custom- columns=NAMESPACE:.metadata.namespace,NAME:.metadata.name,HOSTNETWORK:. spec.hostNetwork --no-headers=true the installation, please refer to the Troubleshooting section and / or seek help on Slack. When do I need to use a kvstore? Unlike the section Quick Installation, this guide explains how to configure0 码力 | 1373 页 | 19.37 MB | 1 年前3
Cilium v1.9 Documentationconnectivity provided by Cilium and NetworkPolicy applies to them: kubectl get pods --all-namespaces -o custom- columns=NAMESPACE:.metadata.namespace,NAME:.metadata.name,HOSTNETWORK:. spec.hostNetwork --no-headers=true the installation, please refer to the Troubleshooting section and / or seek help on Slack. When do I need to use a kvstore? Unlike the section Quick Installation, this guide explains how to configure cluster-1 ? Pull Secret [? for help] ********************************** And set networkType: Cilium: sed -i 's/networkType:\ OVNKubernetes/networkType:\ Cilium/' "${CLUSTER_NAME}/install-config.yaml" Resulting0 码力 | 1263 页 | 18.62 MB | 1 年前3
Cilium v1.6 Documentationthe installation, please refer to the Troubleshooting section and / or seek help on Slack. When do I need to use a kvstore? Unlike the section Quick Installation, this guide explains how to configure previously performed for kube- dns $ kubectl delete pods -n kube-system $(kubectl get pods -n kube-system -o custom-columns=NAME:.metadata.name,HOSTNETWORK:.spec.hostNetwork -- no-headers=true | grep '' following command displays the set of available Kubernetes versions. az aks get-versions -l westus -o table Create an AKS Cluster You can use any method to create and deploy an AKS cluster with the exception 0 码力 | 734 页 | 11.45 MB | 1 年前3
Cilium v1.7 Documentationconnectivity provided by Cilium and NetworkPolicy applies to them: kubectl get pods --all-namespaces -o custom- columns=NAMESPACE:.metadata.namespace,NAME:.metadata.name,HOSTNETWORK:. spec.hostNetwork --no-headers=true the installation, please refer to the Troubleshooting section and / or seek help on Slack. When do I need to use a kvstore? Unlike the section Quick Installation, this guide explains how to configure connectivity to resources outside the cluster (e.g., VMs in the VPC or AWS managed services) is masqueraded (i.e., SNAT) by Cilium to use the VPC IP address of the Kubernetes worker node. Excluding the lines for0 码力 | 885 页 | 12.41 MB | 1 年前3
Cilium v1.8 Documentationconnectivity provided by Cilium and NetworkPolicy applies to them: kubectl get pods --all-namespaces -o custom- columns=NAMESPACE:.metadata.namespace,NAME:.metadata.name,HOSTNETWORK:. spec.hostNetwork --no-headers=true the installation, please refer to the Troubleshooting section and / or seek help on Slack. When do I need to use a kvstore? Unlike the section Quick Installation, this guide explains how to configure connectivity provided by Cilium and NetworkPolicy applies to them: kubectl get pods --all-namespaces -o custom- columns=NAMESPACE:.metadata.namespace,NAME:.metadata.name,HOSTNETWORK:. spec.hostNetwork --no-headers=true0 码力 | 1124 页 | 21.33 MB | 1 年前3
Steering connections to sockets with BPF socket lookup hookwith BPF socket lookup hook Jakub Sitnicki, Cloudflare @jkbs0 @cloudflare October 28-29, 2020 Who am I? ● Software Engineer at Cloudflare Spectrum TCP/UDP reverse proxy, Linux kernel, ... ● Contributor echo_dispatch.bpf.o clang -I…/linux/usr/include -I…/linux/tools/lib -g -O2 -Wall -Wextra -target bpf -c -o echo_dispatch.bpf.o echo_dispatch.bpf.c # bpftool prog load echo_dispatch.bpf.o /sys/fs/bpf/echo_dispatch_prog0 码力 | 23 页 | 441.22 KB | 1 年前3
Debugging the BPF Virtual Machineunderstand how things work ● Sometimes, eBPF programs can’t even load ● I couldn’t find good resources on this, so, here I am ● I break lots of eBPF programs ● The BPF Virtual machine is not easy to understand nux-next.git /source/linux cd linux mkdir build make O=$PWD/build ARCH=x86_64 x86_64_defconfig make O=$PWD/build ARCH=x86_64 menuconfig make O=$PWD/build ARCH=x86_64 -j16 Kernel image Remember to:0 码力 | 10 页 | 233.09 KB | 1 年前3
共 17 条
- 1
- 2













