Skip to main content
Version: Weekly Build

Installation Options

Before provisioning anything, decide on these axes. Each maps directly to a setting in config.yaml; see the private cloud installer config reference for the full schema.

Kubernetes: Codesphere-managed or your own cluster​

By default, OMS installs and manages a k0s cluster on the hosts you provide (kubernetes.managedByCodesphere: true). You can instead bring an already-running Kubernetes cluster — for example a cloud-managed cluster like EKS — by setting kubernetes.managedByCodesphere: false and supplying the cluster's kubeconfig; see Use an existing Kubernetes cluster.

PostgreSQL: installed by OMS or external​

By default, OMS installs and manages PostgreSQL on a host you provide (postgres.mode: install). You can instead point at a PostgreSQL instance you already operate (postgres.mode: external); see Private cloud installer config reference.

Storage: Ceph on dedicated hosts​

Ceph is installed and managed via cephadm on dedicated hosts you provide, and connected into the Kubernetes cluster via Rook as an external-cluster CSI provider; see Architecture and Requirements and sizing for host counts and sizing.

Load balancing: cloud controller, MetalLB, or ExternalIP​

Use a cloud provider's Kubernetes load-balancer integration where available, or MetalLB on infrastructure without one; see Gateway and load balancing.

Registry access​

Codesphere nodes currently pull platform images directly from ghcr.io using credentials Codesphere provides (registry.server: ghcr.io, registry.loadContainerImages: false); see Prepare the jumpbox and generate the configuration. A full installer package that bundles container images (registry.loadContainerImages: true) also exists but is deprecated; see Install steps and profiles.

Scale: evaluation, POC, or production​

Next​

Once these decisions are made, continue to Requirements and sizing or, if infrastructure is already provisioned, straight to the installation guide.