Add support for KubeAPIServer --request-timeout flag

[dntosas]

What type of PR is this?
/kind api-change

What this PR does / why we need it:
Add support for kops to declare --request-timeout flag from kube-apiserver

Which issue(s) this PR fixes:
Addresses #10026

Does this PR introduce a user-facing change?:

Enable users to set timeout value for all kinds of handlers via request-timeout flag on kube-apiserver

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

kind: Cluster
spec:
    kubeAPIServer:
      requestTimeout: "180s"

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

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. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @dntosas!

It looks like this is your first PR to kubernetes/kops 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kops has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @dntosas. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[dntosas]

/retest-cla

[hakman]

Thanks for adding this @dntosas. Should be a pretty useful option.
I added a few comments, mostly nits.
/ok-to-test

[hakman]

Thanks @dntosas !
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dntosas, hakman

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [hakman]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dntosas]

Thanks for adding this @dntosas. Should be a pretty useful option.
I added a few comments, mostly nits.
/ok-to-test

thanks for the comments @hakman and have a nice sunday!

qq: tried a manual testing by cherry-picking this commit on release-1.18 branch and build kops binary from there. what observed, is that although kops does actually update cluster.yaml on remote state and forces a master node rotation, api-server still starts with the default value of request-timeout rather than specified one ^^ maybe we miss something in this commit that prevent actual mapping from happening? still searching for this

[hakman]

@dntosas for this to work you need a full build, including nodeup.

If you want cherrypick to 1.18, please do it using the ckerry-pick script from the kubernetes repo. If you do it soon it may be included in next build.