You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/overview/architecture.mdx
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,11 +29,11 @@ Each plane in OpenChoreo operates as a distinct functional unit, with its own li
29
29
The brain of OpenChoreo. It watches developer- and platform-defined CRDs, validates and processes them, and coordinates activities across other planes. It translates intent such as "deploy this component" or "connect these services" into concrete infrastructure actions.
30
30
31
31
Responsibilities include:
32
-
• Validating CRD instances and resolving references (e.g., Connections between Components)
33
-
• Applying policy and environment-specific rules
34
-
• Coordinating CI jobs, deployments, and observability configurations
35
-
• Reconciling desired state with actual state across all planes
36
-
• Tracking the state of Components across environments and Data Planes
32
+
-Validating CRD instances and resolving references (e.g., Connections between Components)
33
+
-Applying policy and environment-specific rules
34
+
-Coordinating CI jobs, deployments, and observability configurations
35
+
-Reconciling desired state with actual state across all planes
36
+
-Tracking the state of Components across environments and Data Planes
37
37
38
38
The Control Plane is extensible, allowing integration with different backends for image building, observability tooling, environment provisioning, and more.
Copy file name to clipboardExpand all lines: docs/overview/what-is-openchoreo.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ import {versions} from '../_constants.mdx';
10
10
# What is OpenChoreo?
11
11
OpenChoreo is a comprehensive, open-source Internal Developer Platform (IDP) designed for platform engineering (PE) teams who want to streamline developer workflows and deliver Internal Developer Portals without having to build everything from scratch.
12
12
13
-
OpenChoreo orchestrates many CNCF and other projects to provide a comprehensive framework for PE teams to build the platform they want.
13
+
OpenChoreo orchestrates many CNCF and other projects to give platform teams a strong head start, you can use it as-is, or tailor it to fit your own internal developer platform vision.
Copy file name to clipboardExpand all lines: versioned_docs/version-v0.3.x/overview/architecture.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ OpenChoreo is architected as a modular, Kubernetes-native control plane that int
13
13
The Control Plane acts as the orchestrator, transforming high-level platform and developer intent into actionable workloads deployed across Data Planes, while wiring them into the Observability Plane for visibility.
14
14
15
15
The diagram below illustrates how these components interact.
16
-
xz
16
+
17
17
18
18
19
19
Each plane in OpenChoreo operates as a distinct functional unit, with its own lifecycle, scaling behavior, and security boundaries. Together, these planes and supporting interfaces form the core components of the platform:
@@ -29,11 +29,11 @@ Each plane in OpenChoreo operates as a distinct functional unit, with its own li
29
29
The brain of OpenChoreo. It watches developer- and platform-defined CRDs, validates and processes them, and coordinates activities across other planes. It translates intent such as "deploy this component" or "connect these services" into concrete infrastructure actions.
30
30
31
31
Responsibilities include:
32
-
• Validating CRD instances and resolving references (e.g., Connections between Components)
33
-
• Applying policy and environment-specific rules
34
-
• Coordinating CI jobs, deployments, and observability configurations
35
-
• Reconciling desired state with actual state across all planes
36
-
• Tracking the state of Components across environments and Data Planes
32
+
-Validating CRD instances and resolving references (e.g., Connections between Components)
33
+
-Applying policy and environment-specific rules
34
+
-Coordinating CI jobs, deployments, and observability configurations
35
+
-Reconciling desired state with actual state across all planes
36
+
-Tracking the state of Components across environments and Data Planes
37
37
38
38
The Control Plane is extensible, allowing integration with different backends for image building, observability tooling, environment provisioning, and more.
Copy file name to clipboardExpand all lines: versioned_docs/version-v0.3.x/overview/what-is-openchoreo.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ import {versions} from '../_constants.mdx';
10
10
# What is OpenChoreo?
11
11
OpenChoreo is a comprehensive, open-source Internal Developer Platform (IDP) designed for platform engineering (PE) teams who want to streamline developer workflows and deliver Internal Developer Portals without having to build everything from scratch.
12
12
13
-
OpenChoreo orchestrates many CNCF and other projects to provide a comprehensive framework for PE teams to build the platform they want.
13
+
OpenChoreo orchestrates many CNCF and other projects to give platform teams a strong head start, you can use it as-is, or tailor it to fit your own internal developer platform vision.
0 commit comments