Skip to content

Architecture Overview

CPS1 is deployed on your Kubernetes cluster to transparently handle all necessary operations that support its features.

Warning

We strongly recommend that CPS1 must be deployed on a Kubernetes cluster dedicated for development and doesn't have any production workloads.

For more details on how to properly deploy CPS1, refer to the Installing CPS1 guide.

A CPS1 instance has two main components: the Web Console and the Workspace Server.

The Web Console is used by developers and administrators for managing Apps and lauching development environment Workspaces.

The Workspace Server has two services. The first is the API Server that has the Web Console as its client. The second is an Kubernetes Operator that performs operations and listens for events on the cluster's Control Plane to manage the development environment Workspaces lifecycle.

CPS1 Architecture Overview

The Kubernetes Operator extends Kubernetes by combining Custom Resource Definitions, Pods, Deployments, Services, ConfigMaps and many other funcionalities to create development environment Workspaces.

CPS1 makes Kubernetes invisible, providing production-like environments and a seamless cloud-based developer experience. The Kubernetes Operator integrates into the cluster's Control Plane, continuously monitoring the actual state against the desired state and reconciling if configuration drift occurs.