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.
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
Che supports two installation methods:
chectlcommand-line tool-
Install and manage Che from the command line. This method provides the most control over the installation process and supports advanced configuration options during deployment.
- Kubernetes web console
-
Install the Eclipse Che Operator from OperatorHub and create a
CheClusterinstance through the web console. This method uses the standard Kubernetes Operator installation workflow.
Deployment scenarios
- Standard installation
-
Deploy Che on an Kubernetes cluster with internet access. Both the CLI and web console methods are available.
- Restricted environment
-
Deploy Che on an air-gapped or disconnected Kubernetes cluster. This scenario requires mirroring container images to a private registry before installation.
- 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.