Failed to call webhook error fpga.mutator.webhooks.intel.com and sgx.mutator.webhooks.intel.com repeated in kube-apiserver logs
- Dominant language
- Mustache
- Stars
- 19
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
I am seeing repeated errors in the kube-apiserver logs (will paste below), being repeated every 5 minutes. This looks like similar behaviour to issue #46.
I am using charts `intel-device-plugins-gpu` and `intel-device-plugins-operator`, both are version `0.36.0` and installed as `HelmRelease` via Flux.
I would note that I have the gpu resource being made available to pods; however I would want to ensure there is not a configuration error that may cause issues down the line. Thank you in advance for any assistance.
````
W0717 08:25:00.146602 1 dispatcher.go:210] Failed calling webhook, failing open fpga.mutator.webhooks.intel.com: failed calling webhook "fpga.mutator.webhooks.intel.com": failed to call webhook: the server could not find the requested resource
E0717 08:25:00.146626 1 dispatcher.go:214] "Unhandled Error" err="failed calling webhook \"fpga.mutator.webhooks.intel.com\": failed to call webhook: the server could not find the requested resource" logger="UnhandledError"
W0717 08:25:00.146681 1 dispatcher.go:210] Failed calling webhook, failing open fpga.mutator.webhooks.intel.com: failed calling webhook "fpga.mutator.webhooks.intel.com": failed to call webhook: the server could not find the requested resource
E0717 08:25:00.146700 1 dispatcher.go:214] "Unhandled Error" err="failed calling webhook \"fpga.mutator.webhooks.intel.com\": failed to call webhook: the server could not find the requested resource" logger="UnhandledError"
W0717 08:25:00.146747 1 dispatcher.go:210] Failed calling webhook, failing open fpga.mutator.webhooks.intel.com: failed calling webhook "fpga.mutator.webhooks.intel.com": failed to call webhook: the server could not find the requested resource
E0717 08:25:00.146764 1 dispatcher.go:214] "Unhandled Error" err="failed calling webhook \"fpga.mutator.webhooks.intel.com\": failed to call webhook: the server could not find the requested resource" logger="UnhandledError"
W0717 08:25:00.149478 1 dispatcher.go:210] Failed calling webhook, failing open sgx.mutator.webhooks.intel.com: failed calling webhook "sgx.mutator.webhooks.intel.com": failed to call webhook: the server could not find the requested resource
E0717 08:25:00.149496 1 dispatcher.go:214] "Unhandled Error" err="failed calling webhook \"sgx.mutator.webhooks.intel.com\": failed to call webhook: the server could not find the requested resource" logger="UnhandledError"
W0717 08:25:00.150090 1 dispatcher.go:210] Failed calling webhook, failing open sgx.mutator.webhooks.intel.com: failed calling webhook "sgx.mutator.webhooks.intel.com": failed to call webhook: the server could not find the requested resource
E0717 08:25:00.150104 1 dispatcher.go:214] "Unhandled Error" err="failed calling webhook \"sgx.mutator.webhooks.intel.com\": failed to call webhook: the server could not find the requested resource" logger="UnhandledError"
W0717 08:25:00.150166 1 dispatcher.go:210] Failed calling webhook, failing open sgx.mutator.webhooks.intel.com: failed calling webhook "sgx.mutator.webhooks.intel.com": failed to call webhook: the server could not find the requested resource
E0717 08:25:00.150179 1 dispatcher.go:214] "Unhandled Error" err="failed calling webhook \"sgx.mutator.webhooks.intel.com\": failed to call webhook: the server could not find the requested resource" logger="UnhandledError"
````
Contributor guide
Research direction
Start by comparing this report with issue #46 and inspect the intel-device-plugins-gpu and intel-device-plugins-operator HelmRelease deployments at version 0.36.0. Trace the webhook resources registered by those charts and verify the kube-apiserver logs no longer repeat the missing-resource errors while GPU resources remain available to pods.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100