- Shell 71.9%
- Makefile 18.3%
- Go Template 7.2%
- Nix 2.6%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
| .forgejo/workflows | ||
| argocd | ||
| charts | ||
| cluster | ||
| docs | ||
| env | ||
| example | ||
| flux | ||
| hack | ||
| workspaces | ||
| .envrc | ||
| .gitignore | ||
| .yamllint.yaml | ||
| CONTRIBUTING.md | ||
| create-user.sh | ||
| flake.lock | ||
| flake.nix | ||
| GOVERNANCE.md | ||
| LICENSE | ||
| magenta-edge-reg.yaml | ||
| Makefile | ||
| README.md | ||
| renovate.json | ||
| SECURITY.md | ||
POC Core Deploy
Repository for local/core platform bootstrap and GitOps for kcp, APISIX, Zitadel, and controllers.
poc-core-deploy is part of the IPCEI-CIS cloud
infrastructure initiative. Within the IPCEI-CIS edge framework it is the
GitOps deployment layer of the edge-connect platform: ArgoCD reconciles this
repository's main branch into the running environments.
Repository layout
Each directory carries a README describing what lives there and why.
| Directory | Contents |
|---|---|
argocd/ |
ArgoCD Application/ApplicationSet definitions — the app-of-apps, and the only entry point |
env/ |
Per-environment Helm values, env/{dev,local}/<component>.yaml |
cluster/ |
Sources whose ArgoCD destination is the management cluster |
workspaces/ |
Sources synced into kcp logical workspaces, one entry per destination |
charts/ |
Helm charts authored here; directory name matches Chart.yaml |
hack/ |
Bootstrap scripts behind make foundation / make controllers |
example/ |
Sample custom resources, applied by hand — not reconciled |
docs/ |
Operational guides |
The top level names the deployment destination, so a component with both a
management-cluster half and a kcp half appears in both cluster/ and
workspaces/ rather than behind two near-identical root directories.
Documentation
- Platform PKI Setup & CA Rotation - Dedicated per-cluster internal CA management.
- KCP Access for Development and Testing - Connecting as an administrator or tenant user in local and shared-dev environments.
- Local KCP Controller Authentication Probe Guide - Validating projected tokens using the OIDC discovery proxy trust.
- ArgoCD Apply Strategy for KCP Resources - Using client-side diff and apply for KCP logical workspaces.
- Zitadel OIDC Controller Authentication Guide - Authenticating external/provider controllers.
License
Apache-2.0 — see LICENSE.
Funding and Support
This open source project is part of activities carried out within the Important Project of Common European Interest on Next Generation Cloud Infrastructure and Services (IPCEI-CIS) — FKZ 13IPC005, an EU initiative to build a sovereign, interoperable and energy-efficient cloud-to-edge infrastructure in Europe.
The work in this repository has been supported and co-funded by Deutsche Telekom in the context of IPCEI-CIS, where Deutsche Telekom contributes its expertise in secure, sustainable connectivity and cloud-edge platform orchestration for a European cloud-edge continuum.
Where applicable, further national or European public funding instruments associated with IPCEI-CIS may also have contributed to the development of this software.
