Che installation overview

Che deploys on Kubernetes as an Operator that manages a gateway, dashboard, server, and plug-in registry. The installation method you choose — CLI or web console — depends on your cluster environment, security requirements, and need for configuration control.

This page is for platform administrators who install, configure, and manage Che on Kubernetes clusters. To learn more about common roles and example tasks referenced in Che documentation, see Common user roles and tasks.

Che consists of an Operator, a user dashboard, a gateway, and a plug-in registry. The Operator manages the full lifecycle of all server components. You deploy Che by installing the Operator and creating a CheCluster custom resource.

Installation methods

Argo CD (GitOps)

Store the Operator subscription and CheCluster configuration in a Git repository and let Argo CD reconcile the deployment. Choose this method for production deployments where every configuration change must be tracked in Git, auditable, and automatically reconciled.

chectl command-line tool

Install and manage Che from the command line. Choose this method when you need to quickly deploy Che for evaluation or manage it from scripts.

Kubernetes web console

Install the Eclipse Che Operator from OperatorHub and create a CheCluster instance through the web console. This method uses the standard Kubernetes Operator installation workflow.

Deployment scenarios

Standard installation

Deploy Che on a cluster with internet access. All installation methods are available.

GitOps deployment

Your organization manages cluster configuration declaratively through Argo CD. Store the Operator subscription and CheCluster configuration in a Git repository and let Argo CD reconcile the desired state. Available for both connected and air-gapped clusters.

Restricted environment

Deploy Che on an air-gapped or disconnected cluster. This scenario requires mirroring container images to a private registry before installation. Both GitOps and CLI methods are available.

External identity provider

Deploy Che with Keycloak as an external OpenID Connect (OIDC) identity provider instead of the default Kubernetes OAuth. This scenario applies when you need to integrate with an existing identity management system.

Additional resources