Disaster Recovery in Porch
Descriptions of scenarios where one or more Porch data stores are lost or corrupted, with or without backups.
This section provides guidance for diagnosing and resolving common issues with Porch, along with answers to frequently asked questions.
This troubleshooting guide addresses:
Common issues with repository synchronization:
Recovering from data loss scenarios:
If you encounter issues not covered in this guide:
Check Porch logs: Most issues leave traces in the Porch server logs
kubectl logs -n porch-system deployment/porch-server
Verify resource status: Check the status of Porch resources
kubectl get repositories -A
kubectl describe repository <name> -n <namespace>
Search existing issues: Check the Porch GitHub issues
Ask the community:
Report a bug: If you’ve found a bug, open an issue with:
Useful commands for initial troubleshooting:
# Check Porch components are running
kubectl get pods -n porch-system
# Check API service status
kubectl get apiservice v1alpha1.porch.kpt.dev
# List all repositories
kubectl get repositories -A
# Check repository details
kubectl describe repository <name> -n <namespace>
# View Porch server logs
kubectl logs -n porch-system deployment/porch-server --tail=100
# View controller logs
kubectl logs -n porch-system deployment/porch-controllers --tail=100
# List package revisions
kubectl get packagerevisions -A
Descriptions of scenarios where one or more Porch data stores are lost or corrupted, with or without backups.
Common repository sync issues and their solutions