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.
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
Verify the Controller Pod
kubectl get pods -n <namespace>
Running state with 1/1 containers ready.Check Controller Logs
kubectl logs -n <namespace> <controller-pod-name>
Verify RBAC
kubectl get clusterrolebindings | grep <namespace>
kubectl get secrets -n <namespace>
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 |
Verify the EC2 Instance
aws ec2 describe-instances \
--filters "Name=tag:Name,Values=*controller*" \
--query "Reservations[].Instances[].{Id:InstanceId,State:State.Name,IP:PrivateIpAddress}"
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
aws iam list-roles --query "Roles[?contains(RoleName, 'controller')]"
aws secretsmanager list-secrets \
--filters Key=name,Values=<expected-prefix> \
--query "SecretList[].Name"
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 |
Next Steps
