[nri-metadata-injection] DigitalOcean Kubernetes: Mutating webhook with a TimeoutSeconds value greater than 29 seconds will block upgrades

[devurandom]

[nri-metadata-injection] DigitalOcean Kubernetes: Mutating webhook with a TimeoutSeconds value greater than 29 seconds will block upgrades

[devurandom]

I tried setting nri-metadata-injection.timeoutSeconds to 10 myself in Terraform, but that does not seem to have an effect on mutatingwebhookconfigurations/newrelic-infrastructure-nri-metadata-injection, which is still at 30, which I believe is the default.

[devurandom]

I tried setting nri-metadata-injection.timeoutSeconds to 10 myself in Terraform, but that does not seem to have an effect on mutatingwebhookconfigurations/newrelic-infrastructure-nri-metadata-injection, which is still at 30, which I believe is the default.

Setting this to 10 seems to work now, with nri-bundle 2.0.0, but the default is still at 30s, which causes DigitalOcean's Kubernetes linter to complain for the reasons mentioned in https://www.digitalocean.com/docs/kubernetes/resources/clusterlint-errors#admission-controller-webhook-timeout.

[paologallinaharbur]

Yes, since:

name: nri-metadata-injection
version: 1.1.1

such parameter can be configured https://github.com/newrelic/helm-charts/pull/129/files

We would prefer not to change the default value in order to avoid any possible breaking change as specified in the PR