POC Troubleshooting
Common Issues and Solutions
Deployment Issues
Cluster Creation Fails
Problem: Terraform fails to create cluster
Solutions:
Check quotas:
bashgcloud compute project-info describe --project=$PROJECT_IDVerify APIs enabled:
bashgcloud services enable container.googleapis.com compute.googleapis.comCheck permissions:
bashgcloud projects get-iam-policy $PROJECT_ID
Cluster Takes Too Long
Problem: Cluster creation exceeds expected time
Solutions:
- This is normal (5-10 minutes)
- Use smaller cluster (1 node, e2-small)
- Consider using Kind for local POC
Application Issues
Argo Workflows Not Starting
Problem: Argo Workflows pods not running
Solutions:
Check pod status:
bashkubectl get pods -n argo kubectl describe pod <pod-name> -n argoCheck logs:
bashkubectl logs <pod-name> -n argoVerify Helm installation:
bashhelm list -n argo helm status argo-workflows -n argo
Workflows Fail to Execute
Problem: Workflows submit but don't run
Solutions:
Check workflow status:
bashkubectl get workflows -n argo kubectl describe workflow <workflow-name> -n argoCheck node resources:
bashkubectl top nodes kubectl describe node <node-name>Check image pull:
bashkubectl describe pod <workflow-pod> -n argo | grep -i image
Demo Issues
UI Not Accessible
Problem: Can't access Argo Workflows UI
Solutions:
Check service:
bashkubectl get svc -n argoPort forward:
bashkubectl port-forward -n argo svc/argo-workflows-server 2746:2746Check firewall rules:
bashgcloud compute firewall-rules list
Demo Workflows Not Working
Problem: Demo workflows fail or don't appear
Solutions:
Verify workflows deployed:
bashkubectl get workflows -n argoCheck workflow YAML:
bashkubectl get workflow <name> -n argo -o yamlSubmit manually:
bashkubectl apply -f manifests/demo-workflow-simple.yaml
Time Management Issues
POC Running Behind Schedule
Problem: Not meeting timeline
Solutions:
Assess scope:
- Can anything be deferred?
- Are all objectives critical?
Communicate early:
- Inform stakeholders
- Discuss options
- Adjust if needed
Focus on core:
- Prioritize must-have criteria
- Defer nice-to-have
Scope Creep
Problem: POC expanding beyond original scope
Solutions:
Refer to scope document:
- Remind stakeholders of agreed scope
- Document new requests separately
Assess impact:
- Will it affect timeline?
- Is it critical for decision?
Get approval:
- Document scope change
- Get stakeholder sign-off
- Adjust timeline if needed
Communication Issues
Stakeholder Misalignment
Problem: Different expectations
Solutions:
Review scope document:
- Ensure everyone has same understanding
- Clarify any confusion
Regular updates:
- Daily standups
- Weekly status reports
- Immediate issue communication
Document decisions:
- Write down all decisions
- Share with stakeholders
Getting Help
Internal Resources
- Team members
- Technical leads
- Project managers
- Documentation
External Resources
- Vendor support
- Community forums
- Documentation sites
- Stack Overflow
When to Escalate
- Critical blockers
- Timeline at risk
- Scope significantly changing
- Stakeholder concerns
Prevention Tips
- Test Everything First - Don't demo untested workflows
- Have Backup Plan - Always ready for failures
- Document Issues - Track problems and solutions
- Communicate Early - Don't wait for problems to escalate
- Stay Focused - Resist scope creep
- Manage Time - Regular check-ins on progress