From 99ddd1928d9ae7cb7d493a126df7fd5ab354705a Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 20 Feb 2026 09:15:46 +0000
Subject: [PATCH 1/2] Initial plan


From 426cb4a2bd814c75fc77a594c8af3b1c7bfa34b0 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 20 Feb 2026 09:20:39 +0000
Subject: [PATCH 2/2] docs: expand README with comprehensive project overview

Co-authored-by: ron96g <46990708+ron96g@users.noreply.github.com>
---
 README.md | 71 ++++++++++++++++++++++++++++++++++++++++++++++++++++---
 1 file changed, 68 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 1ce4a396..4444394f 100644
--- a/README.md
+++ b/README.md
@@ -15,9 +15,74 @@ SPDX-License-Identifier: CC0-1.0
 
 ## About
 
-As Part of Open Telekom Integration Platform, the Control Plane is the central management layer that governs the operation of your Kubernetes cluster. It maintains the desired state of the system, manages workloads, and provides interfaces for user interaction and automation.
-
-The Control Plane components run on one or more nodes in the cluster and coordinate all cluster activities, including scheduling, monitoring, and responding to events.
+As part of the [Open Telekom Integration Platform](https://github.com/telekom), the Control Plane is the central management layer that governs the operation of your Kubernetes cluster. It maintains the desired state of the system, manages workloads, and provides interfaces for user interaction and automation.
+
+Built on the [Kubernetes Operator pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/), the Control Plane extends native Kubernetes with custom controllers and resources to provide a complete platform for API management, identity, gateway configuration, and organizational governance. It enables teams to declaratively define and expose APIs, manage subscriptions with approval workflows, and integrate with external systems like Kong Gateway and Keycloak — all via Kubernetes-native custom resources.
+
+## Key Features
+
+- **API Lifecycle Management** — Declaratively register, expose, and subscribe to APIs using Rover files or the REST API. Supports full lifecycle from creation to deprecation.
+- **Approval Workflows** — Configurable approval strategies (auto-approve, single-approver, four-eyes principle) with expiration, recertification, and audit trail.
+- **API Gateway Integration** — Automatic configuration of Kong Gateway with routes, consumers, rate limiting, JWT/OAuth2 authentication, and request/response transformation.
+- **Identity & Access Management** — Integration with Keycloak for service account provisioning, realm management, and OAuth2/OIDC token validation.
+- **Organization & Team Management** — Hierarchical group and team structure with automatic namespace provisioning and role-based access control.
+- **Secret & File Management** — Secure secret storage with pluggable backends (Kubernetes Secrets, Conjur) and S3-compatible file storage for OpenAPI specifications.
+- **Notification System** — Multi-channel event notifications via Email, Microsoft Teams, and Webhooks with customizable templates.
+- **Declarative Configuration** — All resources are managed as Kubernetes custom resources, enabling GitOps workflows and infrastructure-as-code practices.
+
+## Architecture
+
+The Control Plane follows a modular architecture organized into three categories:
+
+### Operators (Kubernetes Controllers)
+
+| Operator | Responsibility |
+|----------|---------------|
+| [admin](admin/) | Platform-level resources: Environments, Zones, Remote Organizations |
+| [api](api/) | API lifecycle: APIs, Exposures, Subscriptions, Categories |
+| [application](application/) | Application abstraction with Identity/Gateway provisioning |
+| [approval](approval/) | Approval workflows for API subscription requests |
+| [gateway](gateway/) | Kong Gateway configuration: Routes, Consumers, Realms |
+| [identity](identity/) | Keycloak integration: Clients, Realms, Identity Providers |
+| [organization](organization/) | Team & Group management with namespace auto-provisioning |
+| [rover](rover/) | Declarative user-facing API for exposures and subscriptions |
+| [notification](notification/) | Event-driven notifications via Email, Teams, Webhook |
+
+### API Servers (REST APIs)
+
+| Server | Responsibility |
+|--------|---------------|
+| [rover-server](rover-server/) | REST API for managing Rover exposures, subscriptions, and API specs |
+| [secret-manager](secret-manager/) | RESTful secret storage and retrieval |
+| [file-manager](file-manager/) | File storage for OpenAPI specifications (S3/MinIO backend) |
+| [cpapi](cpapi/) | Read-only REST API across all Control Plane domains |
+
+### Shared Libraries
+
+| Library | Responsibility |
+|---------|---------------|
+| [common](common/) | Shared controller utilities, error handling, and conditions |
+| [common-server](common-server/) | HTTP server library with CRUD, OAuth2, and audit logging |
+
+### CLI Tools
+
+| Tool | Responsibility |
+|------|---------------|
+| [rover-ctl](rover-ctl/) | CLI for CI/CD-friendly access to Rover Server |
+
+## Technology Stack
+
+| Category | Technologies |
+|----------|-------------|
+| **Language** | Go 1.24+ |
+| **Framework** | Kubernetes, Kubebuilder, controller-runtime |
+| **HTTP** | Fiber v2, OAPI-Codegen |
+| **Gateway** | Kong Gateway |
+| **Identity** | Keycloak (OAuth2/OIDC) |
+| **Storage** | Kubernetes etcd (CRDs), S3/MinIO, Redis, Conjur |
+| **Testing** | Ginkgo, Gomega, Testify, go-snaps, Mockery |
+| **Deployment** | Kustomize, Helm |
+| **Documentation** | Docusaurus 3, OpenAPI/Swagger |
 
 ## Documentation