content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
| observability can be used | | | | to provide reliable audit | | | | of the attacker's L3/L4 | | | | and L7 network | | | | connectivity. Traffic sent | | | | by the attacker will be | | | | attributed to the worker | | | | node, and not to a | | | | specific Kubernetes | | | | workload. | +-----------------+---------... | https://github.com/cilium/cilium/blob/main//Documentation/security/threat-model.rst | main | cilium | [
0.013107266277074814,
0.08049570024013519,
0.0425911620259285,
-0.0010868414537981153,
0.05926793813705444,
0.030824199318885803,
0.04639851301908493,
-0.038447413593530655,
-0.025770200416445732,
0.05308537930250168,
-0.034085940569639206,
-0.037340082228183746,
0.04222378879785538,
0.009... | 0.129867 |
+-------------------+--------------------------------------------------+ This attack scenario emphasizes the importance of securing Kubernetes nodes, minimizing the permissions available to container workloads, and monitoring for suspicious activity on the node, container, and API server levels. Recommended Controls ^^... | https://github.com/cilium/cilium/blob/main//Documentation/security/threat-model.rst | main | cilium | [
-0.014040889218449593,
0.09727459400892258,
0.03256668150424957,
-0.014954307116568089,
0.0587812140583992,
-0.008825959637761116,
0.07518616318702698,
-0.05980062112212181,
0.01382235623896122,
0.05756249278783798,
0.020974110811948776,
-0.030810890719294548,
0.033568356186151505,
0.00308... | 0.218826 |
as the attacker can only inject traffic to worker nodes, but not see the replies. .. image:: images/cilium\_threat\_model\_network\_attacker.png For such an attacker, the threat matrix is as follows: .. rst-class:: wrapped-table +------------------+---------------------------------------------------+ | \*\*Threat | \*\... | https://github.com/cilium/cilium/blob/main//Documentation/security/threat-model.rst | main | cilium | [
-0.06425246596336365,
0.08226878941059113,
-0.03886805847287178,
0.040759045630693436,
0.10608170181512833,
-0.061916425824165344,
0.051715388894081116,
0.03688802570104599,
-0.03604770451784134,
0.04631355032324791,
0.041136763989925385,
-0.052744489163160324,
0.10574711859226227,
0.03521... | 0.107173 |
into a multi-node compromise. | +------------------+---------------------------------------------------+ | Cilium eBPF | An attacker with ``kubectl exec`` access to the | | programs | Cilium agent pod will be able to modify eBPF | | | programs. | +------------------+---------------------------------------------------+ ... | https://github.com/cilium/cilium/blob/main//Documentation/security/threat-model.rst | main | cilium | [
-0.025396177545189857,
0.07598397135734558,
-0.012992143630981445,
-0.03504083305597305,
-0.025330597534775734,
0.001200937433168292,
0.013176130130887032,
-0.01821356825530529,
0.05916222184896469,
0.04349711164832115,
0.005574257578700781,
-0.055758461356163025,
0.047108374536037445,
-0.... | 0.18208 |
if such access is suspicious. Hubble Data Attacker ~~~~~~~~~~~~~~~~~~~~ This is an attacker with network reachability to Kubernetes worker nodes, or other systems that store or expose Hubble data, with the goal of gaining access to potentially sensitive Hubble flow or process data. .. image:: images/cilium\_threat\_mod... | https://github.com/cilium/cilium/blob/main//Documentation/security/threat-model.rst | main | cilium | [
-0.015021638944745064,
0.09016972035169601,
-0.018818523734807968,
0.005686597898602486,
0.10683871805667877,
-0.059516552835702896,
0.011611678637564182,
0.02457432448863983,
-0.010646807961165905,
0.02846040204167366,
-0.0028164908289909363,
0.010084384121000767,
0.06927219033241272,
-0.... | 0.103458 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_encryption\_ztunnel: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* Ztunnel Transparent Encryption (Beta) \*\... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/encryption-ztunnel.rst | main | cilium | [
-0.06098497658967972,
0.023706993088126183,
-0.09147433191537857,
0.03190172091126442,
0.010837429203093052,
-0.06051468104124069,
0.0012729703448712826,
-0.0011525930603966117,
0.05764230340719223,
-0.03323918581008911,
0.023319439962506294,
-0.0025880143512040377,
0.061350367963314056,
0... | 0.071962 |
actually enrolled in the StateDB table: .. code-block:: shell-session kubectl exec -n kube-system ds/cilium -- cilium-dbg statedb dump | jq '.["mtls-enrolled-namespaces"]' The results of this query should show which namespaces have been successfully processed by the enrollment reconciler. #. Run a ``bash`` shell in one... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/encryption-ztunnel.rst | main | cilium | [
-0.0384519025683403,
-0.021649034693837166,
0.014807254076004028,
-0.033896978944540024,
-0.032742079347372055,
-0.08844445645809174,
-0.010269254446029663,
-0.03851018846035004,
0.0698019415140152,
0.0028580722864717245,
0.0019088361877948046,
-0.11186638474464417,
0.03448197618126869,
-0... | 0.156521 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_gsg\_encryption: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* Transparent Encryption \*\*\*\*\*\*\*\*\*\*\*\*... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/encryption.rst | main | cilium | [
-0.03998072072863579,
0.04592973366379738,
-0.08062493801116943,
-0.010620695538818836,
0.02493784762918949,
-0.07300268858671188,
-0.000409779284382239,
-0.03396542742848396,
0.03852936252951622,
-0.016952451318502426,
0.030951568856835365,
-0.02836623229086399,
0.04950636997818947,
-0.02... | 0.076766 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io \*\*\*\*\*\*\*\*\*\*\*\* Introduction \*\*\*\*\*\*\*\*\*\*\*\* Cilium provides security on multiple levels. Each can be used individually or c... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/intro.rst | main | cilium | [
-0.002925556618720293,
0.0258632805198431,
-0.12053921073675156,
-0.050289615988731384,
0.009077051654458046,
-0.059382326900959015,
-0.03208377584815025,
0.03555074706673622,
0.0418475940823555,
-0.05741062015295029,
0.041932351887226105,
-0.04073871299624443,
0.022818736732006073,
-0.024... | 0.196443 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_encryption\_ipsec: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* IPsec Transparent Encryption \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/encryption-ipsec.rst | main | cilium | [
-0.043695151805877686,
-0.002738288836553693,
-0.06839996576309204,
-0.02490902878344059,
0.02382839098572731,
-0.04899418354034424,
0.02731994166970253,
-0.0008390489383600652,
0.09048022329807281,
-0.01306458655744791,
0.004700708203017712,
-0.034852590411901474,
0.009750846773386002,
-0... | 0.154394 |
Encryption in Cilium =========================== .. tabs:: .. group-tab:: Cilium CLI If you are deploying Cilium with the Cilium CLI, pass the following options: .. parsed-literal:: cilium install |CHART\_VERSION| \ --set encryption.enabled=true \ --set encryption.type=ipsec .. group-tab:: Helm If you are deploying Cil... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/encryption-ipsec.rst | main | cilium | [
0.027192357927560806,
0.038463249802589417,
-0.023790454491972923,
-0.027765169739723206,
-0.010582544840872288,
-0.040027718991041183,
-0.0073806825093925,
0.01834956370294094,
0.07294990122318268,
0.0019284693989902735,
0.016293387860059738,
-0.07841626554727554,
0.0006341335247270763,
-... | 0.086826 |
xxd -p -c 64) 128\"}}") kubectl patch secret -n kube-system cilium-ipsec-keys -p="${data}" -v=1 During transition the new and old keys will be in use. The Cilium agent keeps per endpoint data on which key is used by each endpoint and will use the correct key if either side has not yet been updated. In this way encrypti... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/encryption-ipsec.rst | main | cilium | [
-0.022648511454463005,
0.009009486064314842,
-0.03100426308810711,
-0.03982828930020332,
-0.055848073214292526,
-0.01541894767433405,
-0.0005895148497074842,
0.01021355390548706,
0.11482325196266174,
0.022285351529717445,
0.044444601982831955,
-0.057354431599378586,
0.02212873101234436,
-0... | 0.151147 |
IPv4 and IPv6 are enabled and no key rotation is ongoing, there should be 8 keys in use on each node. The list of decryption interfaces should have all native devices that may receive pod traffic (for example, ENI interfaces). All XFRM errors correspond to a packet drop in the kernel. The following details operational ... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/encryption-ipsec.rst | main | cilium | [
0.060065366327762604,
-0.04422202333807945,
0.04758985713124275,
-0.027661776170134544,
0.03611021116375923,
-0.056021105498075485,
-0.051019977778196335,
-0.03656120225787163,
0.05903902277350426,
0.02781805582344532,
0.10124984383583069,
0.06713645160198212,
0.00585528276860714,
-0.05402... | 0.031658 |
above XFRM errors, packet drops of type ``No node ID found`` (code 197) may also occur under normal operations. These drops can happen if a pod attempts to send traffic to a pod on a new node for which the Cilium agent didn't yet receive the CiliumNode object or to a pod on a node that was recently deleted. It can also... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/encryption-ipsec.rst | main | cilium | [
0.03901538625359535,
-0.06274418532848358,
0.0024267113767564297,
0.055073291063308716,
0.09106409549713135,
-0.06935033947229385,
0.03386479988694191,
0.014670898206532001,
0.002389847068116069,
0.014182011596858501,
0.037563543766736984,
-0.0499211847782135,
-0.0034216251224279404,
-0.05... | 0.179113 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_arch\_id\_security: \*\*\*\*\*\*\*\*\*\*\*\*\*\* Identity-Based \*\*\*\*\*\*\*\*\*\*\*\*\*\* Container management systems such as Kuberne... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/identity.rst | main | cilium | [
0.0340019091963768,
0.047945138067007065,
-0.04500989243388176,
-0.04610045254230499,
0.03769613802433014,
-0.034850336611270905,
0.03230173513293266,
-0.018485598266124725,
0.0743870809674263,
-0.024950094521045685,
0.020869813859462738,
-0.04553139582276344,
0.038951411843299866,
-0.0308... | 0.256742 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* Policy Enforcement \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* All security policies are described assuming stat... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/policyenforcement.rst | main | cilium | [
-0.05416952073574066,
0.024966023862361908,
-0.10486751794815063,
-0.04026501998305321,
-0.02350015752017498,
-0.027516333386301994,
0.07449622452259064,
-0.030161606147885323,
0.02716469205915928,
0.014224294573068619,
0.04861857369542122,
-0.03142387047410011,
0.09382475912570953,
-0.006... | 0.212348 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_encryption\_wg: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* WireGuard Transparent Encryption \*\*\*\*\*\*\*\*\*\*\*\... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/encryption-wireguard.rst | main | cilium | [
-0.08106858283281326,
0.05552125722169876,
-0.06346071511507034,
-0.02432573027908802,
0.05258374661207199,
-0.06062931567430496,
0.05812114104628563,
-0.00489760423079133,
0.03107949160039425,
-0.02223881706595421,
0.06747821718454361,
-0.04328133538365364,
0.04292099550366402,
0.00126797... | 0.124254 |
verbose output suppressed, use -v or -vv for full protocol decode listening on cilium\_wg0, link-type RAW (Raw IP), capture size 262144 bytes 15:05:24.643427 IP 10.244.1.35.51116 > 10.244.3.78.8080: Flags [S], seq 476474887, win 64860, options [mss 1410,sackOK,TS val 648097391 ecr 0,nop,wscale 7], length 0 15:05:24.644... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/encryption-wireguard.rst | main | cilium | [
-0.010979543440043926,
0.08584070205688477,
-0.08194106072187424,
-0.03367885202169418,
0.05597338080406189,
-0.07263948768377304,
0.009501869790256023,
-0.02926982007920742,
0.0022472720593214035,
0.011515908874571323,
0.009634776040911674,
-0.06036800146102905,
-0.05222001671791077,
-0.0... | 0.101563 |
If you are deploying Cilium with the Cilium CLI, pass the following options: .. parsed-literal:: cilium install |CHART\_VERSION| \ --set encryption.enabled=true \ --set encryption.type=wireguard \ --set encryption.nodeEncryption=true .. group-tab:: Helm If you are deploying Cilium with Helm by following :ref:`k8s\_inst... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/encryption-wireguard.rst | main | cilium | [
-0.0035204917658120394,
0.06644458323717117,
-0.03376704826951027,
0.007786653935909271,
0.010654720477759838,
-0.017287984490394592,
0.02172354981303215,
-0.0012293272884562612,
0.08180193603038788,
0.006988173816353083,
0.02379833720624447,
-0.07630700618028641,
0.02656593546271324,
0.00... | 0.066473 |
| | | | | Service | | | +----------------+-------------------+----------------------+-----------------+ | Client outside | remote Pod via | KPR, | default | | cluster | Service | overlay routing, | | | | | without DSR, | | | | | without XDP | | +----------------+-------------------+----------------------+--------------... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/encryption-wireguard.rst | main | cilium | [
0.0028259342070668936,
-0.030664891004562378,
0.011032377369701862,
-0.028684785589575768,
0.0141372075304389,
-0.06825011223554611,
-0.033093761652708054,
0.013437272980809212,
-0.05151243507862091,
-0.0011360349599272013,
0.055999480187892914,
0.0019159413641318679,
-0.016231879591941833,
... | 0.104791 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_envoy: ===== Envoy ===== Envoy proxy shipped with Cilium is built with minimal Envoy extensions and custom policy enforcement filters. Ci... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/proxy/envoy.rst | main | cilium | [
-0.00013868045061826706,
0.018676094710826874,
-0.03151828050613403,
-0.03651191294193268,
0.035304710268974304,
-0.06766626238822937,
-0.037397198379039764,
-0.038977038115262985,
-0.017541950568556786,
0.019419318065047264,
0.026354791596531868,
-0.040404874831438065,
0.023041000589728355,... | 0.190436 |
of parsing the protocol, and Cilium + Envoy + eBPF do the heavy-lifting. This guide uses simple examples based on a hypothetical "r2d2" protocol (see `proxylib/r2d2/r2d2parser.go `\_) that might be used to talk to a simple protocol droid a long time ago in a galaxy far, far away. But it also points to other real protoc... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/proxy/envoy.rst | main | cilium | [
-0.03231126815080643,
0.005941576324403286,
-0.02847493626177311,
-0.06646550446748734,
-0.08989277482032776,
-0.031891390681266785,
-0.05951714143157005,
0.04642079770565033,
-0.046218711882829666,
-0.00024384056450799108,
-0.04821890965104103,
-0.05856576934456825,
0.04103890806436539,
0... | 0.191766 |
of commands that can be sent over the protocol. In that case, looking at higher-level user documentation can fill in some of these knowledge gaps. Here are examples for `Redis Commands `\_ and `Cassandra CQL Commands `\_ . Another great trick is to use `Wireshark `\_ to capture raw packet data between a client and serv... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/proxy/envoy.rst | main | cilium | [
0.00610301923006773,
0.011327585205435753,
-0.0520419105887413,
0.020040318369865417,
-0.04862966015934944,
-0.037049613893032074,
-0.013689092360436916,
0.042318668216466904,
-0.015166070312261581,
0.048682522028684616,
-0.034494128078222275,
-0.07314276695251465,
0.11054068058729172,
-0.... | 0.0873 |
server to client). OnData is called when there is data to process, and the value of the boolean 'reply' parameter indicates the direction of the stream for a given call to OnData. The data passed to OnData is a slice of byte slices (i.e., an array of byte arrays). The return values of the OnData function tell the Go fr... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/proxy/envoy.rst | main | cilium | [
-0.030830862000584602,
0.015708180144429207,
-0.0391540601849556,
-0.026570970192551613,
-0.02760004997253418,
-0.04993458837270737,
0.13508543372154236,
-0.024049123749136925,
0.04675175994634628,
-0.01798977144062519,
-0.001266875071451068,
0.044362012296915054,
-0.022952387109398842,
0.... | 0.05573 |
first x bytes from the data stream passed to OnData, as they represent a request/reply that should not be forwarded to the client or server based on policy. Don't worry about making onData return a drop right away, as we'll return to DROP in a later step below. - \*\*ERROR y\*\* : The connection contains data that does... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/proxy/envoy.rst | main | cilium | [
-0.06646879017353058,
0.019162064418196678,
-0.0161538515239954,
0.0031477566808462143,
-0.07114215940237045,
-0.09522286057472229,
0.05664260685443878,
-0.01846162974834442,
-0.052155476063489914,
-0.03988280147314072,
-0.03818967193365097,
-0.0036997406277805567,
-0.008049438707530499,
-... | -0.002588 |
strings to binary raw data (see cassandra/cassandraparser\_test.go for an example of this). To run the unit tests, go to proxylib/newproto and run: .. code-block:: shell-session $ go test This will build the latest version of your parser and unit test files and run the unit tests. Step 8: Add More Advanced Parsing ====... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/proxy/envoy.rst | main | cilium | [
0.026963472366333008,
0.047177206724882126,
-0.025745199993252754,
0.030514054000377655,
-0.14424178004264832,
-0.10926375538110733,
-0.05810613930225372,
0.0011416422203183174,
-0.04788161814212799,
0.00488689262419939,
-0.05614031106233597,
-0.1058788150548935,
0.03521840274333954,
-0.03... | -0.008099 |
`}) The following is an example of a policy that would allow READ commands with a file regex of ".\*": .. code-block:: go s.ins.CheckInsertPolicyText(c, "1", []string{` name: "cp2" policy: 2 ingress\_per\_port\_policies: < port: 80 rules: < l7\_proto: "r2d2" l7\_rules: < rule: < key: "cmd" value: "READ" > rule: < key: ... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/proxy/envoy.rst | main | cilium | [
-0.1332232505083084,
0.08558505773544312,
-0.04161427915096283,
-0.03046710602939129,
-0.0054716868326067924,
-0.04855634272098541,
0.07101508975028992,
0.06392758339643478,
-0.07467316091060638,
0.05491220951080322,
0.029932072386145592,
-0.025559041649103165,
0.0737689733505249,
-0.00493... | 0.102467 |
container:id=cass-server f00d::a0b:0:0:bab 10.11.51.247 ready 27333 Disabled Disabled 4 reserved:health f00d::a0b:0:0:6ac5 10.11.92.46 ready 50923 Disabled Disabled 18253 container:id=cass-client f00d::a0b:0:0:c6eb 10.11.175.191 ready One can then invoke the client CLI using that server IP address (10.11.51.247 in the ... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/proxy/envoy.rst | main | cilium | [
0.03158266842365265,
0.10904738306999207,
-0.051349204033613205,
-0.06390900909900665,
-0.06271091103553772,
-0.050394054502248764,
0.01141082588583231,
-0.024691522121429443,
0.03284849599003792,
0.02262248657643795,
-0.007133685518056154,
-0.13185252249240875,
0.049751292914152145,
-0.00... | 0.076878 |
OK for the first rev of your parser not to handle all types of requests, or to have a simplified policy structure in terms of which fields can be matched. However, it is important to know what aspects of the protocol you are not parsing, and ensure that it does not lead to any security concerns. For example, failing to... | https://github.com/cilium/cilium/blob/main//Documentation/security/network/proxy/envoy.rst | main | cilium | [
-0.07362531870603561,
0.030210142955183983,
0.01791599579155445,
-0.007146770134568214,
-0.04546600580215454,
-0.07742546498775482,
0.017400233075022697,
0.006661960389465094,
-0.11202099174261093,
0.004891794640570879,
-0.0351233184337616,
-0.07186150550842285,
0.01825885847210884,
-0.020... | 0.001818 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io Using Kubernetes Constructs In Policy ===================================== This section covers Kubernetes specific network policy aspects. ..... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/kubernetes.rst | main | cilium | [
-0.02691303938627243,
-0.0033314272295683622,
-0.04995269700884819,
-0.0653262585401535,
-0.019328834488987923,
-0.03285996988415718,
-0.010053718462586403,
-0.00036825824645347893,
0.046487145125865936,
0.00654556043446064,
-0.0005107970791868865,
-0.050541359931230545,
0.02351001836359501,... | 0.208489 |
.. literalinclude:: ../../../examples/policies/l3/match-expressions/and-statement.yaml :language: yaml ServiceAccounts ~~~~~~~~~~~~~~~ Kubernetes `Service Accounts `\_ are used to associate an identity to a pod or process managed by Kubernetes and grant identities access to Kubernetes resources and secrets. Cilium supp... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/kubernetes.rst | main | cilium | [
-0.0399862565100193,
0.006171452812850475,
-0.033681582659482956,
-0.0754861906170845,
-0.01623566634953022,
-0.007833439856767654,
0.08688435703516006,
-0.01815338060259819,
0.09834212809801102,
0.05649233236908913,
0.026141317561268806,
-0.04921514540910721,
0.03852033615112305,
-0.01728... | 0.242393 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_network\_policy: .. \_Network Policies: .. \_Network Policy: Overview of Network Policy -------------------------- This page documents th... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/index.rst | main | cilium | [
0.014243786223232746,
0.016411734744906425,
-0.035965677350759506,
-0.06503963470458984,
-0.01341224741190672,
-0.01196861919015646,
0.02678099274635315,
-0.010116142220795155,
0.03595723956823349,
0.019846895709633827,
0.023962346836924553,
-0.05099262297153473,
0.051270581781864166,
-0.0... | 0.188147 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_policy\_guide: .. \_policy\_enforcement\_modes: Policy Enforcement Modes ======================== The configuration of the Cilium agent a... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/intro.rst | main | cilium | [
0.044219911098480225,
0.012201203964650631,
-0.0899362787604332,
-0.049721609801054,
0.03335287421941757,
-0.032607629895210266,
0.0029916835483163595,
-0.014842798002064228,
0.04480715095996857,
0.007568429224193096,
0.05728057399392128,
-0.030562935397028923,
-0.005305171012878418,
-0.00... | 0.178794 |
However, some applications may benefit from receiving explicit rejection notifications instead of experiencing connection timeouts. This can provide faster feedback to applications and improve user experience by reducing wait times. This behavior can be configured with the ``--policy-deny-response`` option: \*\*none\*\... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/intro.rst | main | cilium | [
0.015469078905880451,
0.08277036249637604,
0.06684134155511856,
-0.005022082477807999,
0.02772318571805954,
-0.016080837696790695,
0.025084037333726883,
-0.024610428139567375,
0.03518451377749443,
0.051133736968040466,
-0.012517095543444157,
-0.020114896818995476,
0.005010617896914482,
-0.... | 0.124843 |
Rules cannot be identified by comment. // // +optional Description string `json:"description,omitempty"` } ---- endpointSelector / nodeSelector Selects the endpoints or nodes which the policy rules apply to. The policy rules will be applied to all endpoints which match the labels specified in the selector. For addition... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/intro.rst | main | cilium | [
-0.029761169105768204,
0.055322617292404175,
0.020281925797462463,
-0.03791214898228645,
0.06700602173805237,
-0.012168578803539276,
0.0715317353606224,
-0.03089112974703312,
0.048552338033914566,
0.026569347828626633,
-0.02412385307252407,
-0.07705942541360855,
0.022490205243229866,
-0.02... | 0.177221 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_policy\_caveats: \*\*\*\*\*\*\* Caveats \*\*\*\*\*\*\* Security Identity for N/S Service Traffic ========================================... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/caveats.rst | main | cilium | [
-0.007158446591347456,
0.062384460121393204,
-0.05186021327972412,
-0.05754908174276352,
0.011203257367014885,
-0.03119753487408161,
0.016790486872196198,
0.003661203430965543,
0.07286989688873291,
-0.017160562798380852,
-0.0030457740649580956,
-0.08991536498069763,
0.007123303599655628,
-... | 0.193367 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_policy\_examples: Layer 3 Examples ================ The layer 3 policy establishes the base connectivity rules regarding which endpoints ... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
-0.05547122657299042,
-0.0004307838680688292,
-0.062047217041254044,
-0.08341825008392334,
0.00951423216611147,
-0.004440219607204199,
0.04896610230207443,
-0.03648002818226814,
0.08405770361423492,
-0.020175324752926826,
0.04934793710708618,
-0.03387153893709183,
0.04033749923110008,
-0.0... | 0.25705 |
traffic to an endpoint, this does not mean that all endpoints are allowed to send traffic to this endpoint per their policies. In other words, policy must be configured on both sides (sender and receiver). Egress ~~~~~~ An endpoint is allowed to send traffic to another endpoint if at least one egress rule exists which ... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
0.02004123106598854,
-0.021315649151802063,
-0.01000360120087862,
-0.056836482137441635,
-0.0038957493379712105,
0.012411396019160748,
0.09182839840650558,
-0.033519092947244644,
-0.002558075590059161,
0.022123094648122787,
-0.04021412134170532,
-0.03670983761548996,
0.004304612521082163,
... | 0.062813 |
and egress traffic that applies to an endpoint selector is that the other egress and ingress rules (such as ``fromEndpoints``, ``fromPorts``, ``toEntities``, ``toServices``, and the rest) do not limit the scope of the ``toRequires`` of ``fromRequires`` fields. Pairing other ingress and egress rules with a ``toRequires`... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
-0.04083840548992157,
-0.014062391594052315,
0.012792232446372509,
-0.06560899317264557,
0.025367939844727516,
0.05293520539999008,
0.08518712967634201,
-0.040325336158275604,
0.0029128387104719877,
-0.006260244641453028,
-0.010315656661987305,
-0.0473756417632103,
0.0023482826072722673,
0... | 0.069784 |
represents the health endpoints, used to check cluster connectivity health. Each node managed by Cilium hosts a health endpoint. See `cluster\_connectivity\_health` for details on health checks. unmanaged The unmanaged entity represents endpoints not managed by Cilium. Unmanaged endpoints are considered part of the clu... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
0.03152952343225479,
0.021621715277433395,
-0.03897320479154587,
-0.008928555063903332,
0.0543525367975235,
-0.04982319474220276,
0.02329990826547146,
-0.07499493658542633,
0.07352744042873383,
0.03964468464255333,
0.04421680420637131,
-0.0909983441233635,
0.02792545035481453,
-0.015261080... | 0.282287 |
not have labels associated with them. These are typically external services, VMs or metal machines running in particular subnets. CIDR policy can also be used to limit access to external services, for example to limit external access to a particular IP range. CIDR policies can be applied at ingress or egress. CIDR rule... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
0.031265586614608765,
-0.02106965146958828,
-0.08801776170730591,
-0.07139276713132858,
0.05647987872362137,
0.03584853932261467,
0.06738390773534775,
-0.023313643410801888,
0.050488315522670746,
-0.026438431814312935,
0.08195380121469498,
-0.04900803044438362,
0.02131747640669346,
0.00629... | 0.273922 |
have DNS queryable domain names. The IP addresses provided in DNS responses are allowed by Cilium in a similar manner to IPs in `CIDR based`\_ policies. They are an alternative when the remote IPs may change or are not know prior, or when DNS is more convenient. To enforce policy on DNS requests themselves, see `Layer ... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
-0.05862366408109665,
-0.02850901149213314,
-0.012692767195403576,
-0.04236024618148804,
-0.057187508791685104,
-0.07755056023597717,
-0.024788647890090942,
-0.07394860684871674,
0.052575185894966125,
-0.014440304599702358,
-0.012723424471914768,
-0.05515436455607414,
-0.008875499479472637,
... | 0.090619 |
are automatically expired from the cache. This capacity can be changed using the ``--tofqdns-endpoint-max-ip-per-hostname`` option. As with long-lived connections above, live connections are not expired until they terminate. It is safe to mix long- and short-lived connections from the same Pod. IPs above the limit desc... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
0.00208473252132535,
-0.006061977706849575,
0.007666506338864565,
-0.01858111098408699,
0.014181477017700672,
0.026814963668584824,
0.03280750289559364,
-0.05431238189339638,
0.05436159670352936,
0.08309444785118103,
0.015628185123205185,
0.0450066402554512,
-0.024302544072270393,
-0.01022... | 0.092781 |
policies or independently. It restricts the ability of an endpoint to emit and/or receive packets on a particular ICMP/ICMPv6 type (both type (integer) and corresponding CamelCase message (string) are supported). If any ICMP policy is specified, layer 4 and ICMP communication will be blocked unless it's related to a co... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
-0.021091299131512642,
0.05224961042404175,
-0.02896100841462612,
-0.062076542526483536,
0.00837372150272131,
0.03908047452569008,
0.030309252440929413,
0.009263663552701473,
0.03380168229341507,
-0.004564345348626375,
0.019872508943080902,
-0.08605688810348511,
-0.05381620675325394,
-0.03... | 0.24415 |
\* Closing connection curl: (35) Recv failure: Connection reset by peer command terminated with exit code 35 .. \_l7\_policy: Layer 7 Examples ================ Layer 7 policy rules are embedded into Layer 4 rules and can be specified for ingress and egress. ``L7Rules`` structure is a base type containing an enumeration... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
-0.04696488380432129,
-0.0033747439738363028,
-0.03528480976819992,
-0.03800066560506821,
-0.03720056638121605,
-0.028156500309705734,
-0.05760938301682472,
-0.0472838394343853,
-0.04274853318929672,
0.02719159983098507,
0.031786080449819565,
-0.027465030550956726,
-0.054061535745859146,
0... | 0.013431 |
Host Host is an extended POSIX regex matched against the host header of a request, e.g. ``foo.com``. If omitted or empty, the value of the host header is ignored. Headers Headers is a list of HTTP headers which must be present in the request. If omitted or empty, requests are allowed regardless of headers present. It's... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
-0.054799363017082214,
0.1321021169424057,
0.020501576364040375,
-0.06730113178491592,
0.021333666518330574,
-0.06633798778057098,
0.0055519454181194305,
-0.06512033194303513,
0.014996214769780636,
0.033219970762729645,
-0.04123247414827347,
-0.07299745827913284,
0.04406743869185448,
0.011... | 0.041502 |
overall, but the number coming from each client application (each of which could reside on multiple servers). This id acts as a logical grouping across all requests from a particular client. If omitted or empty, all client identifiers are allowed. Topic Topic is the topic name contained in the message. If a Kafka reque... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
0.008561247028410435,
-0.03772849962115288,
-0.06850460916757584,
-0.023341095075011253,
-0.03171065077185631,
0.028094852343201637,
0.015849148854613304,
-0.04704563319683075,
0.09133089333772659,
0.04007025435566902,
-0.05930224806070328,
-0.06294140219688416,
0.07822920382022858,
-0.000... | 0.067717 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ IPs are obtained via intercepting DNS requests with a proxy. These IPs can be selected with ``toFQDN`` rules. DNS responses are cached within Cilium agent respecting TTL. .. \_DNS Proxy: DNS Proxy ~~~~~~~~~ A DNS Proxy in the agent intercepts egress DNS traffic and records IPs ... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
-0.08360561728477478,
-0.006290880497545004,
-0.01599087193608284,
-0.06652560830116272,
-0.12275463342666626,
-0.06189321354031563,
0.02075745351612568,
-0.04236804321408272,
0.050967030227184296,
-0.009442444890737534,
-0.00918971560895443,
-0.018622800707817078,
-0.013984257355332375,
-... | 0.134089 |
| ✓ | ✓ | | +---------------------+-----------------------+---------+---------+--------+--------+--------+ | \*\*Result for Traffic Connections (Allowed / Denied)\*\* | +---------------------+-----------------------+---------+---------+--------+--------+--------+ | | curl server:81 | Allowed | Allowed | Denied | Denied... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
-0.029807254672050476,
0.06840869039297104,
-0.04703931510448456,
-0.07170874625444412,
-0.06615102291107178,
-0.03893942013382912,
-0.010474215261638165,
-0.05915893614292145,
-0.02349490113556385,
-0.049920372664928436,
0.0463516004383564,
-0.011502589099109173,
0.05536340922117233,
-0.0... | 0.015889 |
7 rules. .. note:: Host L7 DNS policies are a beta feature. Please provide feedback and file a GitHub issue if you experience any problems. .. attention:: Adding layer 7 DNS rules to a host policy enables :ref:`DNS based` host policies at the cost of making all host DNS requests go through the :ref:`DNS Proxy` provided... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
-0.005059709306806326,
-0.04740188643336296,
0.048319701105356216,
-0.0617530420422554,
-0.05592336505651474,
-0.05353196710348129,
-0.08402156829833984,
-0.052774764597415924,
0.04576713964343071,
0.028676817193627357,
-0.017728358507156372,
-0.05582434684038162,
-0.02580181322991848,
-0.... | 0.138286 |
-o custom-columns=NAME:.metadata.name,LABELS:.metadata.labels | grep type:ingress-worker`` to verify labels match the policy. To troubleshoot policies for a given node, try the following steps. For all steps, run ``cilium-dbg`` in the relevant namespace, on the Cilium agent pod for the node, for example with: .. code-b... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/language.rst | main | cilium | [
0.04196878522634506,
0.0825250893831253,
-0.07388754934072495,
0.00559589546173811,
0.021502681076526642,
-0.04759800061583519,
0.013617640361189842,
-0.03473830223083496,
0.04964957386255264,
0.05969729647040367,
0.022783957421779633,
-0.13921472430229187,
0.0007134890183806419,
-0.033110... | 0.167841 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_endpoint\_lifecycle: .. \_Endpoint Lifecycle: Endpoint Lifecycle ================== This section specifies the lifecycle of Cilium endpoi... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/lifecycle.rst | main | cilium | [
-0.06826639920473099,
-0.00823434442281723,
-0.054606031626462936,
0.003522064769640565,
0.027787568047642708,
-0.04336412996053696,
-0.02491643838584423,
-0.017233164981007576,
0.02178684063255787,
-0.03413209319114685,
0.07478905469179153,
-0.07327119261026382,
-0.0009173848084174097,
-0... | 0.190973 |
of "lockdown" when it detects that the policy map is no longer overflowing. When an endpoint is locked down all network traffic, both egress and ingress, will be dropped. Cilium will log a warning that the endpoint has been locked down. If this option is enabled, cluster operators should closely monitor the metric the ... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/lifecycle.rst | main | cilium | [
0.02179822139441967,
0.0019440626492723823,
-0.02386854588985443,
0.025049543008208275,
0.04969821870326996,
-0.009591421112418175,
0.034710902720689774,
0.01409014780074358,
-0.0099229970946908,
0.009705111384391785,
0.0011389694409444928,
-0.01749216951429844,
-0.0368896946310997,
-0.064... | 0.236775 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_policy\_troubleshooting: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\* Troubleshooting \*\*\*\*\*\*\*\*\*\*\*\*\*\*\* Policy Rule to Endpoint Mapping ==... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/troubleshooting.rst | main | cilium | [
-0.0018945022020488977,
0.06861444562673569,
-0.05270425230264664,
-0.024570120498538017,
0.06411982327699661,
-0.040242452174425125,
0.024476205930113792,
0.007252130191773176,
0.017580687999725342,
-0.006970611400902271,
0.06047216057777405,
-0.10470164567232132,
0.06737760454416275,
-0.... | 0.154921 |
list``: .. code-block:: shell-session # cilium-dbg fqdn cache list Endpoint Source FQDN TTL ExpirationTime IPs 725 lookup api.github.com. 3600 2023-02-10T18:16:05.842Z 140.82.121.6 725 lookup support.github.com. 3600 2023-02-10T18:16:09.371Z 185.199.111.133,185.199.109.133,185.199.110.133,185.199.108.133 #. If the traf... | https://github.com/cilium/cilium/blob/main//Documentation/security/policy/troubleshooting.rst | main | cilium | [
-0.04565519839525223,
0.05965058133006096,
-0.11959850043058395,
-0.053459808230400085,
0.03473673388361931,
-0.06808588653802872,
0.061734993010759354,
-0.007078219670802355,
0.07641858607530594,
0.048897549510002136,
0.019379809498786926,
-0.03746369108557701,
-0.02467476576566696,
-0.04... | 0.122056 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_xfrm\_guide: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* XFRM Reference Guide \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* .. note:: This docume... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/xfrm/index.rst | main | cilium | [
0.002678867429494858,
-0.06166737526655197,
-0.1156989187002182,
0.008488724939525127,
0.09111020714044571,
-0.07263953238725662,
0.007661984767764807,
0.0776093453168869,
-0.024157896637916565,
-0.041855912655591965,
0.08698267489671707,
-0.09481676667928696,
0.032023072242736816,
-0.0329... | 0.143569 |
10.56.0.17 proto esp reqid 1 mode tunnel Note that when using tunnel mode as is the case here, we should always see XFRM states matching the template of XFRM OUT policies. That is because, on egress, the states are matched after the template is applied. The IP addresses, the SPI, the protocol, the mode, and the reqid s... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/xfrm/index.rst | main | cilium | [
-0.03721998631954193,
0.0030000878032296896,
0.08070164918899536,
-0.009174061939120293,
0.07568550854921341,
-0.0014949108008295298,
0.09061770886182785,
-0.06531257927417755,
-0.0055499388836324215,
-0.01789850927889347,
0.03109206072986126,
-0.06330131739377975,
-0.00286171305924654,
-0... | 0.005656 |
the same priority, the newest one is used. .. code-block:: bash $ ip xfrm policy # - `src 0.0.0.0/0` is the CIDR to match against the source IP address # - `dst 0.0.0.0/0` is the CIDR to match against the destination IP address src 0.0.0.0/0 dst 0.0.0.0/0 uid 0 # - `dir fwd` states the direction. It defines where in th... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/xfrm/index.rst | main | cilium | [
-0.02202283963561058,
-0.05214344337582588,
-0.03453941270709038,
-0.08614684641361237,
0.14719757437705994,
-0.005146705079823732,
0.03524385765194893,
-0.019517019391059875,
0.019860588014125824,
0.003514316864311695,
0.1303989142179489,
0.0459115132689476,
-0.03152291476726532,
-0.02853... | 0.119023 |
will be # dropped with `XfrmInTmplMismatch`. # - `share any` is not implemented and will always be `any`. level use share any # - `enc-mask ffffffff` Bit mask defining the list of allowed encryption algorithms. # See Encryption algorithms in include/uapi/linux/pfkeyv2.h for the list of possible # values. # - `auth-mask... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/xfrm/index.rst | main | cilium | [
-0.02615201100707054,
0.011914235539734364,
-0.12592262029647827,
-0.032987628132104874,
0.08987725526094437,
-0.04289931803941727,
0.029703011736273766,
-0.024531083181500435,
-0.03575870022177696,
-0.05717795342206955,
0.03279983997344971,
-0.04951716959476471,
-0.010629193857312202,
-0.... | -0.005537 |
# time since the state was last used for a packet. When a soft limit or expiration time # is reached, a notification is sent to userspace via netlink # (`struct xfrm\_user\_expire`). When a hard limit or expiration time is reached, the state # is deleted. limit: soft (INF)(bytes), hard (INF)(bytes) limit: soft (INF)(pa... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/xfrm/index.rst | main | cilium | [
-0.0832059308886528,
-0.042846497148275375,
-0.029496274888515472,
-0.027671318501234055,
0.07281288504600525,
0.017271703109145164,
0.11277132481336594,
0.006818108726292849,
0.04336598515510559,
0.026367127895355225,
0.005011021625250578,
0.029010213911533356,
0.029074111953377724,
0.059... | 0.141073 |
field) of the used XFRM state. - \*\*XfrmInStateInvalid:\*\* If received packet matched an XFRM state that is being deleted or that expired. - \*\*XfrmInTmplMismatch:\*\* - If a packet matches an XFRM policy with a non-optional template, but the template doesn't match any of the XFRM states used to decrypt the packet (... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/xfrm/index.rst | main | cilium | [
-0.020199695602059364,
-0.022043533623218536,
0.006391170434653759,
-0.02697359025478363,
0.09964872896671295,
-0.0064375754445791245,
0.06232638284564018,
-0.037932250648736954,
-0.014418945647776127,
-0.010635264217853546,
0.042092110961675644,
-0.058254458010196686,
0.004521877504885197,
... | 0.033907 |
on current IP family, namespace, and direction), each of its red-black trees is looked up using the source and destination IP addresses. The ``root\_s`` tree contains policies sorted by source IP addresses; the ``root\_d`` tree contains policies sorted by destination IP addresses. In addition, leaf nodes of the ``root\... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/xfrm/index.rst | main | cilium | [
-0.024979280307888985,
0.01817338541150093,
-0.011667663231492043,
-0.04593445360660553,
0.12079326063394547,
-0.04536230117082596,
0.050713371485471725,
-0.037747956812381744,
-0.045521512627601624,
0.06594788283109665,
0.056137487292289734,
0.00875038467347622,
0.04080413281917572,
-0.09... | 0.097359 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_bpf\_guide: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* BPF and XDP Reference Guide \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/index.rst | main | cilium | [
-0.03868376091122627,
-0.01980872079730034,
-0.07580259442329407,
-0.07533149421215057,
0.022978220134973526,
-0.037374064326286316,
0.026251371949911118,
0.05719999596476555,
0.010513991117477417,
-0.009018845856189728,
0.08295446634292603,
-0.07374091446399689,
0.04604089632630348,
-0.06... | 0.192287 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_bpf\_dev: Development Tools ================= Current user space tooling, introspection facilities and kernel control knobs around BPF ar... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.008774539455771446,
-0.07372432947158813,
-0.07754825800657272,
-0.04310503974556923,
0.07816409319639206,
-0.05661220848560333,
-0.04958653077483177,
0.07477093487977982,
-0.022128961980342865,
-0.03752819076180458,
0.034419137984514236,
-0.07812024652957916,
-0.04753018543124199,
-0.07... | 0.174725 |
in order to test BPF functionality (current working directory points to the root of the cloned git tree): .. code-block:: shell-session $ cd tools/testing/selftests/bpf/ $ make $ sudo ./test\_verifier The verifier tests print out all the current checks being performed. The summary at the end of running all tests will d... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.019823512062430382,
-0.0631198137998581,
-0.020489996299147606,
-0.006294488441199064,
0.0623958595097065,
-0.06004820019006729,
-0.04585456848144531,
0.009189186617732048,
0.0032283696345984936,
-0.020213747397065163,
0.043478939682245255,
-0.07632264494895935,
-0.04440220817923546,
-0... | 0.041982 |
BPF back end by default when they package LLVM, therefore installing clang and llvm is sufficient on most recent distributions to start compiling C into BPF object files. The typical workflow is that BPF programs are written in C, compiled by LLVM into object / ELF files, which are parsed by user space BPF ELF loaders ... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.003191098105162382,
-0.03448344022035599,
-0.022373393177986145,
-0.0528852753341198,
0.02007480151951313,
0.025180168449878693,
-0.10580651462078094,
0.07207805663347244,
-0.005663005169481039,
-0.046806033700704575,
-0.021910443902015686,
-0.02825298346579075,
-0.09140507131814957,
-0... | 0.050541 |
LLVM need to be compiled from scratch, the following commands can be used: .. code-block:: shell-session $ git clone https://github.com/llvm/llvm-project.git $ cd llvm-project $ mkdir build $ cd build $ cmake -DLLVM\_ENABLE\_PROJECTS=clang -DLLVM\_TARGETS\_TO\_BUILD="BPF;X86" -DBUILD\_SHARED\_LIBS=OFF -DCMAKE\_BUILD\_T... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.044363852590322495,
-0.02518610469996929,
-0.002913030795753002,
-0.06949196010828018,
0.032221488654613495,
-0.004701823461800814,
-0.10030809789896011,
0.03976535052061081,
-0.007056365255266428,
0.007919473573565483,
-0.03398323431611061,
-0.11324775218963623,
-0.04108075797557831,
-0... | -0.13668 |
-march=bpf -filetype=obj -o xdp-example.o The generated LLVM IR can also be dumped in human readable format through: .. code-block:: shell-session $ clang -O2 -Wall -emit-llvm -S -c xdp-example.c -o - LLVM can attach debug information such as the description of used data types in the program to the generated BPF object... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.007170765660703182,
0.026850998401641846,
-0.05731887370347977,
-0.009888040833175182,
0.06836586445569992,
-0.032777734100818634,
-0.035256750881671906,
0.060633305460214615,
-0.05976252630352974,
-0.022686198353767395,
0.03556274250149727,
-0.0872567668557167,
-0.050099506974220276,
-0... | 0.120959 |
-Xclang -target-feature -Xclang +dwarfris -c xdp-example.c -o xdp-example.o After successful compilation ``pahole`` can be used to properly dump structures of the BPF program based on the DWARF information: .. code-block:: shell-session $ pahole xdp-example.o struct xdp\_md { \_\_u32 data; /\* 0 4 \*/ \_\_u32 data\_end... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.016160547733306885,
0.052912354469299316,
-0.021039435639977455,
-0.053227588534355164,
0.022019580006599426,
-0.07539112120866776,
-0.0013696664245799184,
0.007772382814437151,
-0.0806681215763092,
0.013957097195088863,
0.04222341626882553,
-0.1289457380771637,
-0.033989060670137405,
-... | 0.017625 |
may turn a C switch statement into a switch table lookup and jump operation. Since the switch table is placed in the global read-only section, the bpf program will fail to load. The bpf target does not support switch table optimization. The clang option ``-fno-jump-tables`` can be used to disable switch table generatio... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.056781105697155,
-0.04277042672038078,
-0.042720627039670944,
-0.04270637035369873,
-0.035375144332647324,
-0.01145221572369337,
-0.06428810954093933,
0.06536007672548294,
-0.08621430397033691,
-0.002271727193146944,
-0.005636227782815695,
-0.06725353747606277,
-0.11113078892230988,
-0.0... | 0.023532 |
available.\*\* Shared libraries, etc cannot be used with BPF. However, common library code used in BPF programs can be placed into header files and included in the main programs. For example, Cilium makes heavy use of it (see ``bpf/lib/``). However, this still allows for including header files, for example, from the ke... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.02567298896610737,
-0.016845786944031715,
-0.04976774379611015,
-0.05453949794173241,
0.03565047308802605,
0.02064097858965397,
-0.040983591228723526,
0.005320737138390541,
-0.014823265373706818,
-0.07871368527412415,
-0.018797507509589195,
-0.015246926806867123,
-0.020024990662932396,
... | 0.044391 |
map\_lookup\_elem(&acc\_map, &dir); if (bytes) lock\_xadd(bytes, skb->len); return TC\_ACT\_OK; } \_\_section("ingress") int tc\_ingress(struct \_\_sk\_buff \*skb) { return account\_data(skb, 0); } \_\_section("egress") int tc\_egress(struct \_\_sk\_buff \*skb) { return account\_data(skb, 1); } char \_\_license[] \_\_s... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.059353820979595184,
0.03380408510565758,
-0.09937706589698792,
-0.09557494521141052,
0.035636816173791885,
-0.05037657171487808,
0.08851959556341171,
0.035667575895786285,
-0.014695808291435242,
-0.04928301274776459,
0.06127781793475151,
-0.03762916103005409,
0.03812767192721367,
-0.124... | 0.123018 |
Thus, upon loading of the ``ingress`` program, tc will find that no such map exists in the BPF file system and creates a new one. On success, the map will also be pinned, so that when the ``egress`` program is loaded through tc, it will find that such map already exists in the BPF file system and will reuse that for th... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.060281816869974136,
0.06263552606105804,
-0.04121962562203407,
0.004467464517802,
-0.010469204746186733,
-0.014429762959480286,
0.02498302049934864,
0.045178238302469254,
0.04396925866603851,
0.0023610612843185663,
0.03997573256492615,
-0.05628286674618721,
0.012514605186879635,
-0.0875... | 0.148698 |
# define printk(fmt, ...) \ ({ \ char \_\_\_\_fmt[] = fmt; \ trace\_printk(\_\_\_\_fmt, sizeof(\_\_\_\_fmt), ##\_\_VA\_ARGS\_\_); \ }) #endif The program can then use the macro naturally like ``printk("skb len:%u\n", skb->len);``. The output will then be written to the trace pipe. ``tc exec bpf dbg`` can be used to ret... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.005391231272369623,
0.02965562604367733,
-0.10113193094730377,
0.003444444388151169,
-0.033205680549144745,
-0.011552331037819386,
0.11233920603990555,
0.10227780789136887,
-0.041444625705480576,
-0.06918370723724365,
-0.010504786856472492,
-0.05477265268564224,
0.024193590506911278,
-0.... | 0.095023 |
Tail calls provide the flexibility to atomically alter program behavior during runtime by jumping from one BPF program into another. In order to select the next program, tail calls make use of program array maps (``BPF\_MAP\_TYPE\_PROG\_ARRAY``), and pass the map as well as the index to the next program to jump to. The... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.0057335044257342815,
-0.02145780809223652,
0.0021608448587358,
-0.035174380987882614,
-0.028277074918150902,
-0.053249482065439224,
0.04904378950595856,
0.06016019731760025,
0.06699023395776749,
-0.055030014365911484,
-0.03033277578651905,
0.019942117854952812,
-0.06503906100988388,
-0.0... | 0.215706 |
id and the entry within that map: .. code-block:: shell-session $ llvm-objdump -S --no-show-raw-insn prog\_array.o | less prog\_array.o: file format ELF64-BPF Disassembly of section 1/0: looper: 0: r6 = r1 1: r2 = \*(u32 \*)(r6 + 48) 2: r1 = r2 3: r1 += 1 4: \*(u32 \*)(r6 + 48) = r1 5: r1 = 0 ll 7: call -1 8: r1 = r6 9... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.010606946423649788,
0.11496998369693756,
-0.08931883424520493,
-0.06384190171957016,
0.013274626806378365,
-0.07042291015386581,
0.04757773503661156,
0.06582564860582352,
-0.011804888024926186,
-0.00496467761695385,
0.02197931334376335,
-0.05553727224469185,
-0.05511784180998802,
-0.0674... | 0.144799 |
this, the size of struct may often grow larger than expected. .. code-block:: c struct called\_info { u64 start; // 8-byte u64 end; // 8-byte u32 sector; // 4-byte }; // size of 20-byte ? printf("size of %d-byte\n", sizeof(struct called\_info)); // size of 24-byte // Actual compiled composition of struct called\_info /... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.0022732792422175407,
0.07059206068515778,
-0.04548213258385658,
-0.02827330119907856,
-0.016588909551501274,
-0.09003211557865143,
-0.012707187794148922,
0.13087819516658783,
-0.03828613460063934,
-0.04802035912871361,
0.05536763742566109,
-0.006197284907102585,
-0.0496649332344532,
-0.... | 0.050176 |
example, the compiler will generate less optimized code. Since we've removed the padding, processors will conduct unaligned access to the structure and this might lead to performance degradation. And also, unaligned access might get rejected by verifier on some architectures. However, there is a way to avoid downsides ... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.02214425429701805,
0.07113786041736603,
-0.06684939563274384,
-0.019937101751565933,
0.02165617048740387,
-0.12147579342126846,
-0.018586495891213417,
0.07691846042871475,
-0.016097502782940865,
-0.06253709644079208,
0.05174186825752258,
0.010238053277134895,
-0.03727944567799568,
-0.01... | 0.083412 |
and debugging. All BPF program types supported by iproute2 share the same BPF loader logic due to having a common loader back end implemented as a library (``lib/bpf.c`` in iproute2 source tree). The previous section on LLVM also covered some iproute2 parts related to writing BPF C programs, and later sections in this ... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.011674484238028526,
-0.04664919897913933,
0.0275974553078413,
-0.028042569756507874,
0.03806048259139061,
-0.04021738842129707,
-0.01793813519179821,
0.11126627773046494,
-0.030574981123209,
-0.027608349919319153,
-0.01155942864716053,
-0.021322118118405342,
-0.07199453562498093,
-0.102... | 0.026775 |
ensure received packet are set up linearly within a single page for BPF to read and write into. However, once completed, then most drivers only need to perform an atomic replacement of the program itself when a BPF program is requested to be swapped. In total, XDP supports three operation modes which iproute2 implement... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.017606226727366447,
-0.04019274190068245,
0.050475604832172394,
-0.07560788840055466,
0.02898424118757248,
-0.06345298886299133,
0.046768687665462494,
0.0570162869989872,
-0.04743102192878723,
-0.02676997147500515,
0.05941176041960716,
-0.000037345413147704676,
-0.02653501369059086,
-0.0... | 0.074211 |
on em1 0: (b7) r0 = 1 1: (95) exit # ip link set dev em1 xdpgeneric off And last but not least offloaded XDP, where we additionally dump program information via bpftool for retrieving general metadata: .. code-block:: shell-session # ip -force link set dev em1 xdpoffload obj prog.o # ip link show [...] 6: em1: mtu 1500... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.026062065735459328,
0.02026973105967045,
-0.00362854590639472,
-0.052312783896923065,
0.08590630441904068,
-0.07125838845968246,
0.054545484483242035,
0.028174804523587227,
-0.011285477317869663,
-0.014702253974974155,
0.08535543829202652,
-0.06480243057012558,
0.012704377062618732,
-0.... | 0.03746 |
is processed lockless from ``ingress`` and ``egress`` direction and can also be attached to virtual, queue-less devices such as ``veth`` devices connecting containers. Next to the hook, the ``tc filter`` command selects ``bpf`` to be used in ``da`` (direct-action) mode. ``da`` mode is recommended and should always be s... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.04985075816512108,
0.010661851614713669,
-0.035008665174245834,
-0.06093916296958923,
0.011719164438545704,
-0.010208148509263992,
0.11333944648504257,
-0.02811243198812008,
0.02479841746389866,
0.025811344385147095,
0.0213155597448349,
-0.048918984830379486,
-0.038687702268362045,
-0.1... | 0.127949 |
Thus, creation becomes: .. code-block:: shell-session # tc filter add dev em1 ingress pref 1 handle 1 bpf da obj prog.o sec foobar # tc filter show dev em1 ingress filter protocol all pref 1 bpf filter protocol all pref 1 bpf handle 0x1 prog.o:[foobar] direct-action id 1 tag c5f7825e5dac396f And for the atomic replacem... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.068805031478405,
0.06740190833806992,
0.008591949939727783,
-0.052909135818481445,
-0.0012766080908477306,
-0.042827241122722626,
0.07573145627975464,
-0.0074279592372477055,
0.018638476729393005,
0.061207596212625504,
0.0007091588922776282,
-0.0747029110789299,
-0.009206794202327728,
-... | 0.099867 |
load XDP BPF respectively tc BPF programs with iproute2. There are other various advanced options for the BPF loader that apply both to XDP and tc, some of them are listed here. In the examples only XDP is presented for simplicity. \*\*1. Verbose log output even on success.\*\* The option ``verb`` can be appended for l... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.04371616244316101,
-0.00124258897267282,
0.030532492324709892,
-0.047463592141866684,
0.0625782161951065,
-0.047469884157180786,
0.03342027962207794,
0.09252656251192093,
-0.029874185100197792,
0.012845107354223728,
0.011074651964008808,
-0.06026792898774147,
-0.033521827310323715,
-0.0... | 0.053056 |
the BPF file system. Next the loader will handle all program sections that contain ELF relocation entries for maps, meaning that BPF instructions loading map file descriptors into registers are rewritten so that the corresponding map file descriptors are encoded into the instructions immediate value, in order for the k... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.0003207289264537394,
-0.009595074690878391,
-0.03433762490749359,
-0.06191089749336243,
0.04546590894460678,
-0.018573060631752014,
-0.014342967420816422,
0.03885597363114357,
0.01875290274620056,
-0.045656777918338776,
0.0387786366045475,
0.036773741245269775,
-0.05863484367728233,
-0.1... | 0.199635 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_bpf\_users: Further Reading =============== Mentioned lists of docs, projects, talks, papers, and further reading materials are likely no... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/resources.rst | main | cilium | [
-0.04321272298693657,
-0.014599651098251343,
-0.09947895258665085,
-0.05760309100151062,
0.0825895294547081,
-0.035438939929008484,
0.005317586939781904,
0.09154537320137024,
0.028003022074699402,
-0.051936548203229904,
0.02736564911901951,
-0.05993538349866867,
-0.0005770159768871963,
-0.... | 0.23401 |
to collect metrics through a variety of agents as well as analyze collected systems' performance metrics in real-time or by using historical data. With pmdabcc, PCP has a BCC based performance metrics domain agent which extracts data from the kernel via BPF and BCC. https://github.com/performancecopilot/pcp .. \* \*\*W... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/resources.rst | main | cilium | [
-0.015253630466759205,
-0.01292530819773674,
-0.10180716216564178,
-0.008746065199375153,
0.0017614230746403337,
-0.0028651945758610964,
0.03320314362645149,
0.013063318096101284,
0.0033605482894927263,
-0.021343950182199478,
-0.02872033789753914,
-0.06393095850944519,
-0.04230818897485733,
... | 0.177739 |
The library is used by other kernel projects such as perf and bpftool. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/lib/bpf .. \* \*\*bpftool\*\* bpftool is the main tool for introspecting and debugging BPF programs and BPF maps, and like libbpf is developed by the Linux kernel communit... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/resources.rst | main | cilium | [
-0.04090934991836548,
-0.02999640628695488,
-0.0780518427491188,
-0.04613006114959717,
0.09446628391742706,
-0.03390873968601227,
-0.006942823063582182,
0.08052397519350052,
-0.019844839349389076,
-0.06589953601360321,
0.004082772880792618,
-0.04553687945008278,
-0.05872292071580887,
-0.08... | 0.216929 |
Present, and Future, Ferris Ellis, https://ferrisellis.com/posts/ebpf\_past\_present\_future/ 28. Mar 2017, Analyzing KVM Hypercalls with eBPF Tracing, Suchakra Sharma, https://suchakra.wordpress.com/2017/03/31/analyzing-kvm-hypercalls-with-ebpf-tracing/ 27. Jan 2017, Golang bcc/BPF Function Tracing, Brendan Gregg, htt... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/resources.rst | main | cilium | [
-0.01828615367412567,
0.010745612904429436,
-0.036845654249191284,
-0.036483246833086014,
-0.006337242666631937,
-0.030560173094272614,
-0.00587038416415453,
0.04272386059165001,
-0.05400505289435387,
-0.019891653209924698,
0.033631034195423126,
-0.12033607065677643,
-0.040927160531282425,
... | 0.159212 |
for the Rest of Us, Andy Gospodarek, Jesper Dangaard Brouer, https://netdevconf.info/2.1/slides/apr7/gospodarek-Netdev2.1-XDP-for-the-Rest-of-Us\_Final.pdf 35. Mar 2017, SCALE15x, Pasadena, Linux 4.x Tracing: Performance Analysis with bcc/BPF, Brendan Gregg, https://www.slideshare.net/brendangregg/linux-4x-tracing-perf... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/resources.rst | main | cilium | [
-0.005538312718272209,
0.0009746068972162902,
0.02541913464665413,
-0.06071075052022934,
0.05754933878779411,
-0.09953302890062332,
0.016048332676291466,
0.07143672555685043,
-0.017082151025533676,
-0.00966697558760643,
0.006549172103404999,
-0.004646409302949905,
0.00886205118149519,
-0.0... | 0.1622 |
0. Feb 2014, DevConf.cz, Brno, tc and cls\_bpf: lightweight packet classifying with BPF, Daniel Borkmann, http://borkmann.ch/talks/2014\_devconf.pdf Further Documents ----------------- - Dive into BPF: a list of reading material, Quentin Monnet (https://qmonnet.github.io/whirl-offload/2016/09/01/dive-into-bpf/) - XDP -... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/resources.rst | main | cilium | [
-0.023027919232845306,
-0.052472762763500214,
0.01244270708411932,
-0.08388527482748032,
0.061172567307949066,
-0.014717316254973412,
0.09635636955499649,
0.015645697712898254,
-0.05799616128206253,
-0.007370246108621359,
-0.02250179462134838,
-0.026405390352010727,
-0.03955230861902237,
-... | 0.12167 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_bpf\_architect: BPF Architecture ================ BPF does not define itself by only providing its instruction set, but also by offering ... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.013014661148190498,
-0.016848590224981308,
-0.08939240127801895,
-0.060132794082164764,
0.026179105043411255,
-0.04550046846270561,
-0.026155535131692886,
0.08219607174396515,
0.04533897340297699,
-0.07033544778823853,
0.0015800079563632607,
-0.05635026842355728,
-0.021329637616872787,
... | 0.274556 |
maintained throughout updates via BPF maps. \* BPF provides a stable ABI towards user space, and does not require any third party kernel modules. BPF is a core part of the Linux kernel that is shipped everywhere, and guarantees that existing BPF programs keep running with newer kernel versions. This guarantee is the sa... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.03353578597307205,
-0.07223623245954514,
-0.023471098393201828,
-0.09153547883033752,
0.0706842690706253,
-0.031499359756708145,
0.010646146722137928,
0.04235706478357315,
0.03701185807585716,
-0.04577810689806938,
0.01459694467484951,
0.01910330168902874,
-0.031827013939619064,
-0.0769... | 0.262649 |
Register ``r0`` is also the register containing the exit value for the BPF program. The semantics of the exit value are defined by the type of program. Furthermore, when handing execution back to the kernel, the exit value is passed as a 32 bit value. Registers ``r1`` - ``r5`` are scratch registers, meaning the BPF pro... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.04631365090608597,
-0.08545218408107758,
-0.07688456773757935,
0.006292003206908703,
-0.03472846746444702,
0.01601552590727806,
0.07148940116167068,
0.08886696398258209,
0.0007799954037182033,
-0.013418258167803288,
-0.05794103816151619,
-0.029925957322120667,
-0.03025142475962639,
-0.0... | 0.160208 |
``BPF\_K`` for immediate-based operations respectively). In the latter case, the destination operand is always a register. Both ``dst\_reg`` and ``src\_reg`` provide additional information about the register operands to be used (e.g. ``r0`` - ``r9``) for the operation. ``off`` is used in some instructions to provide a ... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.05481201037764549,
-0.011641236953437328,
-0.07193003594875336,
-0.01926591247320175,
-0.041456349194049835,
-0.050284985452890396,
0.06333602219820023,
0.09011074900627136,
0.026605691760778427,
-0.014117160812020302,
0.04035931080579758,
0.047307711094617844,
-0.02292376197874546,
-0.... | 0.231973 |
to ``off + 1`` is performed, otherwise the next instruction (``0 + 1``) is performed. This fall-through jump logic differs compared to cBPF and allows for better branch prediction as it fits the CPU branch predictor logic more naturally. Available conditions are jeq (``==``), jne (``!=``), jgt (``>``), jge (``>=``), js... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.059037622064352036,
-0.031883370131254196,
-0.05299845337867737,
-0.003692458849400282,
0.004877019673585892,
0.010353866964578629,
-0.04109715297818184,
0.12313523888587952,
-0.028861526399850845,
-0.03805261850357056,
-0.015062947757542133,
-0.01576671563088894,
0.021248361095786095,
... | 0.081099 |
be JIT compiled in a transparent and efficient way, meaning that the JIT compiler only needs to emit a call instruction since the register mapping is made in such a way that BPF register assignments already match the underlying architecture's calling convention. This allows for easily extending the core kernel with new... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.08926986157894135,
-0.06379768997430801,
-0.011149265803396702,
-0.05802348256111145,
0.04016053304076195,
-0.006330331787467003,
0.056323885917663574,
0.09758888930082321,
-0.0010309885255992413,
-0.07442592829465866,
0.023214874789118767,
-0.0801435112953186,
-0.09077367186546326,
-0.... | 0.187607 |
of disadvantages come along with them: User space applications can make use of most file descriptor related APIs, file descriptor passing for Unix domain sockets work transparently, etc, but at the same time, file descriptors are limited to a processes' lifetime, which makes options like map sharing rather cumbersome t... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.02145261876285076,
-0.01247383188456297,
-0.03947661444544792,
-0.023113803938031197,
0.03808174282312393,
0.008832619525492191,
-0.01372036337852478,
0.11667052656412125,
0.05953764542937279,
0.004270227625966072,
0.0430726483464241,
0.0335700698196888,
-0.000858797924593091,
-0.070348... | 0.19455 |
from BPF helper calls and BPF tail calls, a more recent feature that has been added to the BPF core infrastructure is BPF to BPF calls. Before this feature was introduced into the kernel, a typical BPF C program had to declare any reusable code that, for example, resides in headers as ``always\_inline`` such that when ... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.04055710509419441,
0.0198870450258255,
0.013087032362818718,
0.02009330876171589,
0.062311071902513504,
-0.0186210535466671,
0.024693196639418602,
0.0638444796204567,
0.04377597197890282,
-0.027443096041679382,
0.03966948762536049,
0.0033237645402550697,
-0.03895626217126846,
-0.0628458... | 0.088098 |
stack when a program execution is at func2. Once the final function (func3) function terminates, all the previous stack frames will be unwinded and control will get back to the caller of BPF program caller. The kernel introduced additional logic for detecting this feature combination. There is a limit on the stack size... | https://github.com/cilium/cilium/blob/main//Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.037007685750722885,
-0.10847653448581696,
-0.039606716483831406,
-0.05917217209935188,
0.009302915073931217,
-0.04797228425741196,
0.009605031460523605,
0.07809971272945404,
0.07038514316082001,
-0.03543949872255325,
-0.03177119418978691,
-0.04502853751182556,
-0.06498011946678162,
-0.0... | 0.09606 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.