> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/self-managed-enterprise-edition/use-self-managed-enterprise-edition/smp-installationupgrade/operator-installation/prerequisites/kubernetes-cluster-requirements.md).

# Kubernetes cluster requirements

Review the resource profiles and node sizing required before you install with the SMP Operator.

Your cluster must provide enough capacity for the deployment scale you expect, and you set that scale through a resource profile. This topic covers the available profiles and the namespace you install into.

### Resource profiles <a href="#resource-profiles" id="resource-profiles"></a>

The Harness Platform uses **resource profiles** to match your deployment scale. Select a profile based on your expected usage.

The following table lists each profile with the concurrent pipeline capacity, the team size it suits, and the YAML file that defines it.

| Profile    | Concurrent Pipelines | Recommended Team Size | YAML File              |
| ---------- | -------------------- | --------------------- | ---------------------- |
| **Small**  | Up to 50             | Fewer than 50 users   | `override-small.yaml`  |
| **Medium** | Up to 200            | 50 to 200 users       | `override-medium.yaml` |
| **Large**  | Over 200             | 200+ users            | `override-large.yaml`  |

Set the profile during installation.

{% tabs %}
{% tab title="helm" %}

```yaml
cluster:
  profile: medium
```

{% endtab %}

{% tab title="clustermgr" %}

```bash
--pi-set cluster.profile=medium
```

{% endtab %}
{% endtabs %}

For detailed resource allocations per profile, see the [Harness resource profiles documentation](/self-managed-enterprise-edition/use-self-managed-enterprise-edition/smp-basic-configuration.md#resource-profiles).

### Namespace configuration <a href="#namespace-configuration" id="namespace-configuration"></a>

Install the platform into a dedicated namespace. Specify the namespace with whichever method you use to install.

{% tabs %}
{% tab title="helm" %}
Use `helm install ... -n <namespace> --create-namespace`.
{% endtab %}

{% tab title="clustermgr" %}
Use `--namespace <namespace>`. The default namespace is `harness`.
{% endtab %}
{% endtabs %}

{% @harness-feedback/feedback %}