Installation
This topic covers how you install the Harness SMP Operator into an existing Kubernetes cluster. You can deploy it with either Helm, using the platform-installer Helm chart directly, or with the clustermgr CLI.
Installation methods
Both methods deploy the same underlying Helm chart, so select the one that fits your operational workflow.
- helm: Use the
platform-installerHelm chart directly withhelm install. - clustermgr: Use the
clustermgrCLI, which bootstraps the Helm chart for you.
For more information on cluster sizing, storage class, registry access, DNS, and TLS certificate requirements, see Prerequisites.
If you install with Helm, install kubectl and helm and configure kubectl with cluster admin access. The clustermgr package bundles both tools.
Installation paths
The install guide covers the full deployment with either Helm or clustermgr. The remaining topics apply to specific environments: use the air-gapped topic if your cluster has no internet access, the discovery topic if you already run Harness SMP and want the operator to discover it, and the FIPS topic if you deploy in a regulated environment. The post-installation checks confirm that the deployment succeeded.
- Install with the SMP Operator: Deploy the Harness Platform with Helm or clustermgr, using either Nginx or Istio ingress.
- Air-gapped installation: Mirror images to a private registry and install offline.
- Discovery: Extract configuration from an existing Harness SMP installation so the operator discovers it.
- FIPS-compliant installation: Configure Istio components to enforce FIPS cryptographic standards.
- Post-installation checks: Verify that the operator deployed successfully.
Next steps
After the installation completes and your checks pass, tune the deployment and look up the parameters you used.
- CLI reference: Review the complete
helmandclustermgrparameter reference. - Advanced configuration: Tune resource sizing and pod security context.
- Upgrade: Upgrade an existing SMP Operator installation.