DevFW-CICD/kcp-katalis-provider
18
0
Fork 0
Code Issues 1 Pull requests 6 Projects Releases 2 Packages Wiki Activity Actions
No description
6 commits 9 branches 3 tags 188 KiB
  • Go 85.6%
  • Smarty 6.3%
  • Makefile 6.2%
  • Dockerfile 1.9%
Find a file
Exact
mawu 04fe260df0
All checks were successful
ci-main / test (push) Successful in 1m1s
Details
chore: migrate Go module path and image refs to edp.buildth.ing/devfw-cicd 
Replace gitlab.devops.telekom.de/ipcei-cis/infra/kcp-katalis-provider
with edp.buildth.ing/devfw-cicd/kcp-katalis-provider in go.mod, imports,
chart values, and documentation links.
2026-05-21 09:05:33 +02:00
.forgejo/workflows ci: add forgejo workflows, goreleaser, makefile parity 2026-05-20 15:16:34 +02:00
chart chore: migrate Go module path and image refs to edp.buildth.ing/devfw-cicd 2026-05-21 09:05:33 +02:00
cmd/provider chore: migrate Go module path and image refs to edp.buildth.ing/devfw-cicd 2026-05-21 09:05:33 +02:00
config FB-04 M0+M1: bootstrap provider repo 2026-04-29 14:51:43 +02:00
docs chore: migrate Go module path and image refs to edp.buildth.ing/devfw-cicd 2026-05-21 09:05:33 +02:00
internal FB-04 M0+M1: bootstrap provider repo 2026-04-29 14:51:43 +02:00
invariants FB-04 M0+M1: bootstrap provider repo 2026-04-29 14:51:43 +02:00
.gitignore FB-04 M0+M1: bootstrap provider repo 2026-04-29 14:51:43 +02:00
.goreleaser.yaml ci: add forgejo workflows, goreleaser, makefile parity 2026-05-20 15:16:34 +02:00
Dockerfile FB-04 M0+M1: bootstrap provider repo 2026-04-29 14:51:43 +02:00
Dockerfile.goreleaser ci: add forgejo workflows, goreleaser, makefile parity 2026-05-20 15:16:34 +02:00
go.mod chore: migrate Go module path and image refs to edp.buildth.ing/devfw-cicd 2026-05-21 09:05:33 +02:00
go.sum FB-04 M0+M1: bootstrap provider repo 2026-04-29 14:51:43 +02:00
LICENSE FB-04 M0+M1: bootstrap provider repo 2026-04-29 14:51:43 +02:00
Makefile ci: add forgejo workflows, goreleaser, makefile parity 2026-05-20 15:16:34 +02:00
README.md chore: migrate Go module path and image refs to edp.buildth.ing/devfw-cicd 2026-05-21 09:05:33 +02:00
renovate.json fix(deps): bump Go to 1.25.10 + add renovate config 2026-05-20 15:22:12 +02:00

README.md

kcp-katalis-provider

Status: ⛔ Not started — planning phase. Slice: FB-04 — Federation bridging controller Owns API surface: operator-federation.edge-connect.eu/v1alpha1 Bridges to: Katalis OPG EWBI operator (opg.ewbi.nby.one/v1beta1)

Purpose

A kcp APIExport provider that translates customer-facing operator-federation CRDs (defined in edge-connect-portal-poc/crds/operator-federation-*.yaml) into Katalis OPG EWBI resources, and reflects status back to the customer-facing surface.

Naming follows the established convention in this codebase:

Repo Upstream Customer-facing API surface
kcp-karmada-provider Karmada placement / fleet
kcp-cilium-mesh-provider Cilium networking.edge-connect.eu
kcp-katalis-provider Katalis (OPG EWBI) operator-federation.edge-connect.eu

What this repo contains

Planning artifacts (this round). No Go code yet.

Path Purpose
docs/PLAN.md Slice plan: scope, non-goals, dependencies, phasing
invariants/FB-04.md Invariants the bridge must uphold (BP / CP / SN)
docs/scenarios.md Scenario matrix (golden / invariant / integration / e2e)
docs/architecture.md Reconciler shape, watches, status linkage

Authoritative references

  • Customer-facing CRDs (leading): edge-connect-portal-poc/crds/operator-federation-*.yaml
  • Customer-facing surface design: edge-connect-portal-poc/docs/operator-federation.md
  • Katalis upstream: org.etsi.osl.controllers.camara/QoDProvisioning/ and opg-ewbi-operator/
  • Architecture decisions:
    • ADR-0007 — Provider portability via providerRef (sibling concept)
    • ADR-0016 (portal-poc) — Customer-resource projection pattern (workspace-scoped routing)
    • ADR-0017 (architecture repo) — Federation surface, three layers
  • Invariants on the customer-facing layer: edge-connect-architecture/invariants/FB-00.md

Out of scope (deliberate)

  • Customer-facing CRD schema changes (lives in edge-connect-portal-poc/crds/).
  • GSMA OPG.04 wire-format compliance (lives in opg-ewbi-operator).
  • Frontend or BFF code (lives in edge-connect-portal-poc).
  • Multi-Katalis-instance federation (one Katalis per operator instance; multiple operators are FB-02 territory).

Ownership

Telco & Edge team (Team 7 in team-topology).