Cilium v1.6 Documentation
-n kube-system $CILIUM_POD /bin/bash root@minikube:~# Next, start Cilium monitor, and limit the output to only “l7” type messages using the “-t” flag: root@minikube:~# cilium monitor -t l7 Listening ‘verdict’ indicating whether the request was allowed by policy (‘Forwarded’ or ‘Denied’). Example output is below. All requests are from empire-outpost to cass-server. The first two requests are allowed synchronized correctly by running cilium bpf ipcache list or cilium map get cilium_ipcache. The output must contain pod IPs from local and remote clusters. If this fails: Is the IP cache information0 码力 | 734 页 | 11.45 MB | 1 年前3Cilium v1.7 Documentation
Rate Limiting Default Rate Limits Configuration Automatic Adjustment Metrics Understanding the log output Configuration Core Agent Monitoring & Metrics Installation cilium-agent cilium-operator Troubleshooting unit tests on code changes BPF and XDP Reference Guide BPF Architecture Instruction Set Helper Functions Maps Object Pinning Tail Calls BPF to BPF Calls JIT Hardening Offloads Toolchain Development Environment -n kube-system $CILIUM_POD /bin/bash root@minikube:~# Next, start Cilium monitor, and limit the output to only “l7” type messages using the “-t” flag: root@minikube:~# cilium monitor -t l7 Listening0 码力 | 885 页 | 12.41 MB | 1 年前3Cilium v1.11 Documentation
unit tests on code changes BPF and XDP Reference Guide BPF Architecture Instruction Set Helper Functions Maps Object Pinning Tail Calls BPF to BPF Calls JIT Hardening Offloads Toolchain Development Environment account show --query "id" --output tsv) AZURE_NODE_RESOURCE_GROUP=$(az aks show --resource-group ${RESOURCE_GROUP} --name ${CLUSTER_NAME} --query "nodeResourceGroup" -- output tsv) AZURE_SERVICE_PRINCIPAL=$(az /subscriptions/${AZURE_SUBSCRIPTION_ID}/resourceGroups/${AZURE_NODE_RES OURCE_GROUP} --role Contributor --output json --only-show-errors) AZURE_TENANT_ID=$(echo ${AZURE_SERVICE_PRINCIPAL} | jq -r '.tenant') AZ0 码力 | 1373 页 | 19.37 MB | 1 年前3Cilium v1.8 Documentation
unit tests on code changes BPF and XDP Reference Guide BPF Architecture Instruction Set Helper Functions Maps Object Pinning Tail Calls BPF to BPF Calls JIT Hardening Offloads Toolchain Development Environment set cluster name: CLUSTER_NAME="cluster-1" Now, create configuration files: Note The sample output below is showing the AWS provider, but it should work the same way with other providers. $ openshift-install 0.0/14 \ --set config.bpfMasquerade=false \ --set global.endpointRoutes.enabled=true \ --output-dir "${OLDPWD}" Copy Cilium manifest to ${CLUSTER_NAME}/manifests: for component in config agent0 码力 | 1124 页 | 21.33 MB | 1 年前3Cilium v1.9 Documentation
unit tests on code changes BPF and XDP Reference Guide BPF Architecture Instruction Set Helper Functions Maps Object Pinning Tail Calls BPF to BPF Calls JIT Hardening Offloads Toolchain Development Environment 30 Connected Nodes: 4/4 If Hubble Relay reports that all nodes are connected, as in the example output above, you can now use the CLI to observe flows of the entire cluster: hubble --server localhost:4245 30 Connected Nodes: 4/4 If Hubble Relay reports that all nodes are connected, as in the example output above, you can now use the CLI to observe flows of the entire cluster: hubble --server localhost:42450 码力 | 1263 页 | 18.62 MB | 1 年前3Cilium v1.10 Documentation
unit tests on code changes BPF and XDP Reference Guide BPF Architecture Instruction Set Helper Functions Maps Object Pinning Tail Calls BPF to BPF Calls JIT Hardening Offloads Toolchain Development Environment account show --query "id" --output tsv) AZURE_NODE_RESOURCE_GROUP=$(az aks show --resource-group ${RESOURCE_GROUP} --name ${CLUSTER_NAME} --query "nodeResourceGroup" -- output tsv) AZURE_SERVICE_PRINCIPAL=$(az /subscriptions/${AZURE_SUBSCRIPTION_ID}/resourceGroups/${AZURE_NODE_RES OURCE_GROUP} --role Contributor --output json --only-show-errors) AZURE_TENANT_ID=$(echo ${AZURE_SERVICE_PRINCIPAL} | jq -r '.tenant') AZ0 码力 | 1307 页 | 19.26 MB | 1 年前3Cilium v1.5 Documentation
-n kube-system $CILIUM_POD /bin/bash root@minikube:~# Next, start Cilium monitor, and limit the output to only “l7” type messages using the “-t” flag: root@minikube:~# cilium monitor -t l7 Listening ‘verdict’ indica�ng whether the request was allowed by policy (‘Forwarded’ or ‘Denied’). Example output is below. All requests are from empire-outpost to cass-server. The first two requests are allowed -y install tcpdump Check that traffic is encrypted: tcpdump -n -i cilium_vxlan tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on cilium_vxlan, link-type EN10MB (Ethernet)0 码力 | 740 页 | 12.52 MB | 1 年前3
共 7 条
- 1