[ https://issues.apache.org/jira/browse/YUNIKORN-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Condit closed YUNIKORN-1153. ---------------------------------- Resolution: Won't Do > Admission controller: first health check should be delayed > ---------------------------------------------------------- > > Key: YUNIKORN-1153 > URL: https://issues.apache.org/jira/browse/YUNIKORN-1153 > Project: Apache YuniKorn > Issue Type: Bug > Components: shim - kubernetes > Reporter: Peter Bacsko > Assignee: Ryan Lo > Priority: Minor > > When deploying Yunikorn locally, I often see the first health check failing: > {noformat} > Events: > Type Reason Age From Message > ---- ------ ---- ---- ------- > Normal Scheduled 3m12s default-scheduler Successfully > assigned default/yunikorn-admission-controller-78c775cfd9-6pp8d to minikube > Normal Pulled 3m12s kubelet Container > image "apache/yunikorn:admission-latest" already present on machine > Normal Created 3m12s kubelet Created > container yunikorn-admission-controller > Normal Started 3m11s kubelet Started > container yunikorn-admission-controller > Warning Unhealthy 2m52s (x2 over 3m2s) kubelet Startup probe > failed: Get "https://192.168.49.2:9089/health": dial tcp 192.168.49.2:9089: > connect: connection refused > {noformat} > We need to add some {{initialDelaySeconds}} to wait with the first probe. > 10-15 seconds is probably a good value. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org For additional commands, e-mail: dev-h...@yunikorn.apache.org