Skip to content

Architecture

The platform has been specifically designed such that customers can deploy and manage their Kubernetes clusters in both cloud and on-premise environments. The Platform has two primary components that are described below.

System Architecture

The Controller

The Controller is a management platform that customers use to manage both their Kubernetes clusters and their containerized applications. A separate interface is provided for Operations and Application Owners to ensure that there is clear separation of duties. The controller can be accessed via a web console, the RCTL CLI, REST APIs and a Terraform provider.

Controller Access

The Controller can be accessed via

  • Using a web browser (via the Web Console) or
  • Programmatically using the RCTL CLI or
  • Programmatically via REST APIs or
  • A Terraform provider

Access Methods

Deployment Options

Three deployment options are supported for the Controller:

  1. SaaS (Multi Tenant, Managed)
  2. Self Hosted (Managed, Single/Multi Tenant)
  3. Self Hosted (Customer Managed, Single/Multi Tenant)

Controller Deployment Options

Kubernetes Mgmt Operator

Every "managed Kubernetes cluster" has a Kubernetes Management operator deployed into a dedicated namespace for ongoing operations and lifecycle management. This Kubernetes operator running on the remote Kubernetes cluster "Dials Out" to the Controller and maintains a long running, TLS connection (mutually authenticated and encrypted).

Important

No inbound ports need to be opened at the firewall. Only outbound on port 443 to the Controller is required.