PageSourceSearch

https://archive-os-3-29.netlify.app/assets/js/9ede52b9.202f6453.js

js archive-os-3-29.netlify.app collected 2026-10-03 10:28:43 UTC 1,747 bytes, 1 lines download raw bytes

1"use strict";(self.webpackChunktigera_docs=self.webpackChunktigera_docs||[]).push([["171"],{66381(e,t,r){r.r(t),r.d(t,{metadata:()=>n,default:()=>p,frontMatter:()=>s,contentTitle:()=>d,toc:()=>l,assets:()=>h});var n=JSON.parse('{"id":"reference/architecture/index","title":"Architecture","description":"Understand Calico components, network design, and the data path between workloads.","source":"@site/calico_versioned_docs/version-3.29/reference/architecture/index.mdx","sourceDirName":"reference/architecture","slug":"/reference/architecture/","permalink":"/calico/3.29/reference/architecture/","draft":false,"unlisted":false,"editUrl":"https://github.com/tigera/docs/edit/main/calico_versioned_docs/version-3.29/reference/architecture/index.mdx","tags":[],"version":"3.29","frontMatter":{"description":"Understand Calico components, network design, and the data path between workloads.","hide_table_of_contents":true},"sidebar":"calicoSidebar","previous":{"title":"Connection tracking","permalink":"/calico/3.29/reference/host-endpoints/conntrack"},"next":{"title":"Component architecture","permalink":"/calico/3.29/reference/architecture/overview"}}'),c=r(70689),i=r(3413),a=r(82567),o=r(81675);let s={description:"Understand Calico components, network design, and the data path between workloads.",hide_table_of_contents:!0},d="Architecture",h={},l=[];function u(e){let t={h1:"h1",header:"header",...(0,i.R)(),...e.components};return(0,c.jsxs)(c.Fragment,{children:[(0,c.jsx)(t.header,{children:(0,c.jsx)(t.h1,{id:"architecture",children:"Architecture"})}),"\n","\n",(0,c.jsx)(a.A,{items:(0,o.$S)().items})]})}function p(e={}){let{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,c.jsx)(t,{...e,children:(0,c.jsx)(u,{...e})}):u(e)}}}]);

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.