Edge Connect documentation
Feature descriptions and how-to guides for the Edge Connect components. Each section is taken from the component's own repository, so the component team owns and maintains its content.
Components
| Component | Description | Code |
|---|---|---|
| Edge-Connect Deploy | Provides the GitOps deployment layer for Edge Connect. ArgoCD reconciles the component configuration into the target environments. | Code |
| Edge Cloud Build | Build workflows and resources for the IPCEI-CIS edge cloud. | Code |
| Edge Cloud Director | Provides regional API routing, user accounts, authentication, and role-based access control for the edge cloud. | Code |
| Edge Cloud Platform | Manages edge sites, applications, clusters, and application instances. Provides application discovery, automatic provisioning, metrics, and alerts. | Code |
| Edge Cloud Sample Apps | Demonstrates edge application discovery, cloudlet selection, network tests, edge events, and computer vision through the SDK demo app. | Code |
| Edge Cloud UI | Provides the Edge Cloud console for operators and application developers who use telco edge infrastructure. | Code |
| Carbon Data Collector | Collects electricity carbon intensity and renewable share data from ENTSO-E. Publishes ClusterCarbonMetrics for carbon-aware workload placement on Karmada clusters. | Code |
| Domain Provider Controller | Reconciles tenant ProviderCredential resources across KCP workspaces. Reports credential registration and synchronization status without exposing credential values. | Code |
| Kubernetes MCP Evaluation | Measures whether an AI agent can discover and use Edge Connect custom resources through a generic Kubernetes MCP server. Compares context arms and produces CRD-authoring feedback. | Code |
| KCM Proof of Concept | Resolves tenant Kubernetes cluster requests into provider-specific machine types. Selects providers and node pool sizes from requested CPU and memory capabilities. | Code |
| Infrastructure as Code | Infrastructure-as-code configuration for the IPCEI-CIS system. | Code |
Publishing your component's docs
- Put user-facing docs (overview, features, how-to, concepts) in
docs/user/in your repository. Keep operational topics (runbooks, deployment, on-call) indocs/ops/. Maintainers can list them inoperationalDocsto publish them as clearly marked secondary content. - Optionally keep a
CHANGELOG.mdat the repository root. - Ask the docs maintainers to add your component to
components.yamlin the docs hub repository. See How publishing works for the full flow.