Cannot safely upgrade digital ocean cluster due to clusterlint error

[boukeversteegh]

NGINX Ingress controller version: 0.46
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.0", GitCommit:"af46c47ce925f4c4ad5cc8d1fca46c7b77d13b38", GitTreeState:"clean", BuildDate:"2020-12-08T17:59:43Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.7", GitCommit:"132a687512d7fb058d0f5890f07d4121b3f0a2e2", GitTreeState:"clean", BuildDate:"2021-05-12T12:32:49Z", GoVersion:"go1.15.12", Compiler:"gc", Platform:"linux/amd64"}

Environment:

• Cloud provider or hardware configuration: Digital Ocean

What happened:

A new cluster patch upgrade is available for Digital Ocean. However, I am not able to safely upgrade, due to an error produced by clusterlint. I received the following mail from Digital Ocean:

New minor patch version 1.20.8-do.0 has been released, for your Kubernetes cluster datastack.

During our initial upgrade check we found errors that would prevent us from upgrading this cluster safely.

• Validating webhook with a TimeoutSeconds value greater than 29 seconds will block upgrades.

From the Digital Ocean cluster management page, the following error shows.

What you expected to happen:

• I can safely upgrade my cluster
• clusterlint does not report errors on any resources created by ingress-controller for digital ocean.

How to reproduce it:

• Set up a Digital Ocean cluster with version 1.20.7-do.0 (I'm not sure how to do this, my cluster was simply running this version)
• Install the ingress controller.

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v0.46.0/deploy/static/provider/do/deploy.yaml

• Then try to upgrade

/kind bug

[tao12345666333]

#7319 has been merged. Should we close this? This will be available as soon as the v1 goes GA.

[longwuyuan]

Yes we should close it

[strongjz]

/close

[k8s-ci-robot]

@strongjz: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.