Mit Desai created YUNIKORN-3075:
-----------------------------------
Summary: YuniKorn (1.5.2) Webhooks fail after admission controller
redeployment k8s-1.30
Key: YUNIKORN-3075
URL: https://issues.apache.org/jira/browse/YUNIKORN-3075
Project: Apache YuniKorn
Issue Type: Bug
Components: shim - kubernetes
Affects Versions: 1.5.2
Reporter: Mit Desai
We have noticed that when the kubernetes cluster is upgraded to 1.30, Installed
version of YuniKorn does not get affected. It runs without any issues.
However, after the upgrade, if the admission controller has to be redeployed,
the webhooks will be recreated and this could potentially cause problems.
At Visa, we use a modified version of the webhook where we also have a
namespaed scope to schedule yunikorn pods in specific namespaces. When the
admission controller created the webhooks after redeployment, the code built on
go 1.29 was not able to successfully create the webhooks with namespaced scope.
This issue was silently ignored and the webhooks were created with the cluster
level scope. So all the applications in our clusters started to get scheduled
by YuniKorn where they should not have.
--
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
