You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 16, 2023. It is now read-only.
When specifying resource requests and limitations for onyxia-api pod in the Helm chart values.yaml file, the pod will keep on crashing, even after saying in the logs that it has started. The pod crashes and restarts permanently.
Values of the requests and limitations have little to no effect on the restart, and it is presumed that the cause is not related to resource usage, but to an unexpected party yet to be uncovered.
Last logs
Collecting the last logs before the crash, using kubect logs -n onyxia <pod> gave:
2022-08-04 09:53:38.841 INFO 1 --- [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 1 endpoint(s) beneath base path '/actuator'
2022-08-04 09:53:39.151 INFO 1 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path ''
2022-08-04 09:53:39.251 INFO 1 --- [ main] fr.insee.onyxia.api.Application : Started Application in 40.702 seconds (JVM running for 44.579)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Rsource limitation/request doesn't work
Issue
onyxia-api
: version 0.14When specifying resource requests and limitations for
onyxia-api
pod in the Helm chartvalues.yaml
file, the pod will keep on crashing, even after saying in the logs that it has started. The pod crashes and restarts permanently.Values of the requests and limitations have little to no effect on the restart, and it is presumed that the cause is not related to resource usage, but to an unexpected party yet to be uncovered.
Last logs
Collecting the last logs before the crash, using
kubect logs -n onyxia <pod>
gave:The text was updated successfully, but these errors were encountered: