> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Verify Your Installation

After completing the installation and configuration steps, here's how to confirm everything is working.

## Check the Setup Interface

The setup interface shows a progress tracker with five phases. When all phases show a green checkmark, installation is complete and the application is ready for deployment.

## Verify from Your Infrastructure

<Tabs>
  <Tab title="Kubernetes">
    ### Verify the Controller Pod

    ```bash theme={null}
    kubectl get pods -n <namespace>
    ```

    You should see the controller pod in a `Running` state with `1/1` containers ready.

    ### Check Controller Logs

    ```bash theme={null}
    kubectl logs -n <namespace> <controller-pod-name>
    ```

    The logs should show successful startup and a connection established to our systems.

    ### Verify RBAC

    ```bash theme={null}
    kubectl get clusterrolebindings | grep <namespace>
    ```

    You should see the cluster role bindings created during installation.

    ### Verify Secrets (If Configured)

    ```bash theme={null}
    kubectl get secrets -n <namespace>
    ```

    Any secrets you created during configuration should appear here.

    ### Common Issues

    | Symptom                                        | Likely Cause                    | Fix                                                   |
    | ---------------------------------------------- | ------------------------------- | ----------------------------------------------------- |
    | Pod stuck in `Pending`                         | Insufficient cluster resources  | Check node capacity: `kubectl describe nodes`         |
    | Pod in `CrashLoopBackOff`                      | Configuration error             | Check logs: `kubectl logs -n <namespace> <pod>`       |
    | Pod in `ImagePullBackOff`                      | Registry access issue           | Verify your cluster can pull images from the internet |
    | Setup interface shows "Waiting for controller" | Controller hasn't connected yet | Wait 2-5 minutes; check outbound network access       |
  </Tab>

  <Tab title="AWS">
    ### Verify the EC2 Instance

    ```bash theme={null}
    aws ec2 describe-instances \
      --filters "Name=tag:Name,Values=*controller*" \
      --query "Reservations[].Instances[].{Id:InstanceId,State:State.Name,IP:PrivateIpAddress}"
    ```

    The instance should be in a `running` state.

    ### Verify Connectivity

    The controller communicates outbound to our systems. You can verify it's connected by checking the setup interface - the controller status will show as online.

    ### Verify IAM Roles

    ```bash theme={null}
    aws iam list-roles --query "Roles[?contains(RoleName, 'controller')]"
    ```

    The IAM role created during setup should appear with the expected permissions.

    ### Verify Secrets (If Configured)

    ```bash theme={null}
    aws secretsmanager list-secrets \
      --filters Key=name,Values=<expected-prefix> \
      --query "SecretList[].Name"
    ```

    Any secrets you created during configuration should appear here.

    ### Common Issues

    | Symptom                                        | Likely Cause                    | Fix                                                    |
    | ---------------------------------------------- | ------------------------------- | ------------------------------------------------------ |
    | Instance in `stopped` or `terminated`          | IAM or quota issue              | Check CloudTrail for errors                            |
    | Instance not starting                          | Insufficient instance quota     | Request a limit increase in your AWS account           |
    | Instance running but not connecting            | Outbound access blocked         | Verify security group allows outbound HTTPS (port 443) |
    | Setup interface shows "Waiting for controller" | Controller hasn't connected yet | Wait 2-5 minutes; check NAT gateway and route tables   |
  </Tab>
</Tabs>

For more detailed troubleshooting, see [Troubleshooting](/customer/operations/troubleshooting).

## Next Steps

* [Monitoring and Health](/customer/operations/monitoring) - Track ongoing status
* [Permissions](/customer/security/permissions) - Understand what the controller can access
* [Updates and Upgrades](/customer/operations/updates-and-upgrades) - How we ship changes