The default webhook timeout of 1s is causing grief for us sometimes, especially when we apply large amounts of manifests at the same time, using kubectl apply -f <path to directory>. This change simply adds the option to increase the timeout (which has anecdotally helped in our case), while leaving the default at 1s.
Here's an example of the problem I'm trying to solve:
history.go:53: [debug] getting history for release harbor
install.go:172: [debug] Original chart version: "8.0.0"
install.go:189: [debug] CHART PATH: /root/.cache/helm/repository/harbor-8.0.0.tgz
client.go:108: [debug] creating 46 resource(s)
Error: Internal error occurred: failed calling webhook "k-rail.cruise-automation.github.com": Post https://k-rail.k-rail.svc:443/?timeout=1s: context deadline exceeded
helm.go:94: [debug] Internal error occurred: failed calling webhook "k-rail.cruise-automation.github.com": Post https://k-rail.k-rail.svc:443/?timeout=1s: context deadline exceeded
Hey dudes!
The default webhook timeout of 1s is causing grief for us sometimes, especially when we apply large amounts of manifests at the same time, using
kubectl apply -f <path to directory>. This change simply adds the option to increase the timeout (which has anecdotally helped in our case), while leaving the default at 1s.Here's an example of the problem I'm trying to solve: