-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Read deployment failure from Kubernetes events #402
Read deployment failure from Kubernetes events #402
Comments
|
A sort of. In case of requesting for too many CPU cores, like this: resources:
cpu_min: 10M # 10M is not millis, but Mega Kubernetes says it's okay on
Good question. Probably it's going to end up in kubernetes plugin, but if possible we could bring some generic parts into the Lifecycle (in order not to repeat the same thing in many plugins). |
Sometimes deployment of a job gets stuck, if for instance, Kubernetes can't create a new pod due to not enough resources in the cluster. Deployment commands succeeds (
kubectl apply
), but the real deployment process happens in background later on, and then Kubernetes states that cluster is out of memory and reports an error event. However, Racetrack doesn't know that and still waits patiently until the pod is created, until the timeout occurs. It makes the deployment proceess unnecessarily long in this case.It would be better to read the k8s events or get notified in this case, to show a meaningful error to a user and abort immediately as the error happens.
The text was updated successfully, but these errors were encountered: