> 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/install/post-installation-checks.md).

# Post-installation checks

Verify that the SMP Operator was deployed successfully.

After the installation completes, you can verify that the Harness SMP Operator deployed successfully before you use it.

Run the checks against the namespace you installed the operator in. Work through the sections in order to confirm the pod, StatefulSet, logs, Helm release, and ingress, then sign in to the Installer UI. The examples use the `harness` namespace, so substitute your own namespace if you installed into a different one.

***

### Verify Operator Pod <a href="#verify-operator-pod" id="verify-operator-pod"></a>

Confirm that the operator pod is running.

```bash
# Check pods
kubectl get pods -n harness | grep platform-installer

# Expected: platform-installer-0  1/1  Running
```

***

### Verify StatefulSet <a href="#verify-statefulset" id="verify-statefulset"></a>

Confirm that the `StatefulSet` that manages the operator pod reports its replica as ready.

```bash
kubectl get statefulset -n harness

# Expected: platform-installer  1/1
```

***

### Check Operator Logs <a href="#check-operator-logs" id="check-operator-logs"></a>

Read the logs from the `pi` container in the operator pod.

```bash
kubectl logs -n harness platform-installer-0 -c pi
```

***

### Verify Helm Release <a href="#verify-helm-release" id="verify-helm-release"></a>

Confirm that the `platform-installer` Helm release is present and note the version it deployed.

```bash
helm list -n harness

# Expected: platform-installer  harness  1  <version>
```

***

### Verify Ingress <a href="#verify-ingress" id="verify-ingress"></a>

Check the ingress resources for the ingress type you installed with.

#### nginx (default) <a href="#nginx-default" id="nginx-default"></a>

Confirm the ingress resource and the nginx service exist.

```bash
kubectl get ingress -n harness
kubectl get svc -n harness | grep nginx
```

#### Istio <a href="#istio" id="istio"></a>

Check the Istio pods, Helm releases, Gateway, and VirtualService, then retrieve the external IP of the ingress gateway.

```bash
# Check Istio pods
kubectl -n harness get pods -l app=istiod
kubectl -n harness get pods -l app=istio-ingressgateway

# Check Helm releases
helm list -n harness | grep istio

# Check Gateway
kubectl -n harness get gateway

# Check VirtualService
kubectl -n harness get vs

# Get ingress gateway external IP
kubectl -n harness get svc istio-ingressgateway
```

***

### Access the Installer UI <a href="#access-the-installer-ui" id="access-the-installer-ui"></a>

After the checks above pass, sign in to the Installer UI.

Open in a browser:

```
https://<YOUR_DNS>/pi
```

Login with the admin email and password provided during installation.

For more information on troubleshooting common issues, see [Troubleshooting & Support](/self-managed-enterprise-edition/use-self-managed-enterprise-edition/smp-installationupgrade/operator-installation/troubleshooting.md).

{% @harness-feedback/feedback %}