Verify Installation¶

After installation is complete, you can verify your installation with the following steps.

Health Check Endpoint¶

Both deployment methods provide the same health check endpoint to verify the Pixee Enterprise service status:

curl https://<domain or ip>/q/health

Expected response:

{
    "status": "UP",
    "checks": [
        {
            "name": "SmallRye Reactive Messaging - liveness check",
            "status": "UP"
        },
        {
            "name": "Pixee Server health check",
            "status": "UP",
            "data": {
                "server-version": "2024-11-03-653a81d"
            }
        },
        {
            "name": "Database connections health check",
            "status": "UP",
            "data": {
                "<default>": "UP"
            }
        },
        {
            "name": "SmallRye Reactive Messaging - readiness check",
            "status": "UP"
        },
        {
            "name": "SmallRye Reactive Messaging - startup check",
            "status": "UP"
        }
    ]
}

Kubernetes Resources¶

Embedded ClusterHelm Deployment

To verify Kubernetes resources in Embedded Cluster deployments follow:

Open a terminal session on the VM and run the following commands:
```
sudo ./pixee shell
kubectl get all -n kotsadm
```
Verify the Pixee Enterprise Server is ready by viewing pods and services, making sure all are in the ready state.

To verify Kubernetes resources in Helm Deployment follow:

Verify the application is properly deployed by viewing pods and services, making sure all are in the ready state:

kubectl get all -n pixee-enterprise-server

GitHub App Connectivity¶

If you enabled GitHub integration and created a custom GitHub app, you can verify your GitHub App connectivity by checking your GitHub App's event log.

This log can be accessed through your GitHub App's settings under the "Advanced" section. See GitHub.com for more information.