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

Kubernetes
AWS

Verify the Controller Pod

kubectl get pods -n <namespace>

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

Check Controller Logs

kubectl logs -n <namespace> <controller-pod-name>

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

Verify RBAC

kubectl get clusterrolebindings | grep <namespace>

You should see the cluster role bindings created during installation.

Verify Secrets (If Configured)

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

Verify the EC2 Instance

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

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)

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

For more detailed troubleshooting, see Troubleshooting.

Next Steps

Monitoring and Health - Track ongoing status
Permissions - Understand what the controller can access
Updates and Upgrades - How we ship changes

Getting Started

Installation

Configuration

Security

Operations

Reference

Verify Your Installation

Check the Setup Interface

Verify from Your Infrastructure

Verify the Controller Pod

Check Controller Logs

Verify RBAC

Verify Secrets (If Configured)

Common Issues

Verify the EC2 Instance

Verify Connectivity

Verify IAM Roles

Verify Secrets (If Configured)

Common Issues

Next Steps

​Check the Setup Interface

​Verify from Your Infrastructure

​Verify the Controller Pod

​Check Controller Logs

​Verify RBAC

​Verify Secrets (If Configured)

​Common Issues

​Verify the EC2 Instance

​Verify Connectivity

​Verify IAM Roles

​Verify Secrets (If Configured)

​Common Issues

​Next Steps

Check the Setup Interface

Verify from Your Infrastructure

Verify the Controller Pod

Check Controller Logs

Verify RBAC

Verify Secrets (If Configured)

Common Issues

Verify the EC2 Instance

Verify Connectivity

Verify IAM Roles

Verify Secrets (If Configured)

Common Issues

Next Steps