Deploy failed with signal SIGABRT
If your deployment failed with this error message it means the pod gotSIGABRT signal from the k8s cluster it runs on - It usually indicates a crash due to memory limitation.
In this case, define requests and limits for the pod size as described in Custom/optional configuration.
Next steps
- Custom/optional configuration - Set resource requests and limits for deployment pods.
- Monitoring Self-Hosted Agents - Check agent state and connectivity status.
- Self-hosted Kubernetes agent - Reinstall or upgrade the agent Helm chart.