Yongjun Zhang created YUNIKORN-1817:
---------------------------------------
Summary: k8s API server can't reach the admission controller
Key: YUNIKORN-1817
URL: https://issues.apache.org/jira/browse/YUNIKORN-1817
Project: Apache YuniKorn
Issue Type: Task
Components: core - scheduler
Reporter: Yongjun Zhang
In our newer cluster, we ran into the issue that the API server can't
find/reach the admission controller:
{code:java}
dispatcher.go:142] Failed calling webhook, failing open
admission-webhook.yunikorn.validate-conf: failed calling webhook
"admission-webhook.yunikorn.validate-conf": failed to call webhook: Post
"https://yunikorn-admission-controller-service.yunikorn.svc:443/validate-conf?timeout=10s":
context deadline exceeded
dispatcher.go:184] failed calling webhook
"admission-webhook.yunikorn.mutate-pods": failed to call webhook: Post
"https://yunikorn-admission-controller-service.yunikorn.svc:443/mutate?timeout=10s":
service "yunikorn-admission-controller-service" not found
E0316 01:11:35.199066 10 dispatcher.go:184] failed calling webhook
"admission-webhook.yunikorn.mutate-pods": failed to call webhook: Post
"https://yunikorn-admission-controller-service.yunikorn.svc:443/mutate?timeout=10s":
service "yunikorn-admission-controller-service" not found
{code}
In our earlier test cluster, we did not hit the same issue. It should be some
configuration diff. Log this issue for record.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
