How the installation works
Che deploys on Kubernetes as an Operator that manages a gateway, dashboard, server, and plug-in registry. The installation method you choose depends on your cluster environment 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
chectlcommand-line tool-
Choose this method when you need to quickly deploy Che for evaluation, customize the
CheClusterconfiguration during installation, or manage Che from scripts. - Kubernetes web console
-
Choose this method when you prefer a graphical workflow through OperatorHub and do not need advanced configuration options during deployment.
Both methods produce the same result: an Operator subscription and a CheCluster custom resource. For step-by-step deployment instructions, see Additional resources.
Deployment scenarios
- Standard deployment
-
Your Kubernetes cluster has internet access. Both installation methods are available. The Operator pulls container images directly from
registry.redhat.io. - Air-gapped deployment
-
Your cluster has no internet access. Mirror the required container images and Operator catalogs to a private registry before installation.
- External identity provider
-
Your organization manages authentication through an existing identity system such as Keycloak. Deploy Che with an external OIDC provider instead of the default Kubernetes OAuth.