Add missing kube api-server config for alpha tests

[upodroid]

/cc @hakman

stuck on this error

apiserver flag diffs https://www.diffchecker.com/66T6W3uy/ (left is kops, right is kube-up)

I1001 14:57:02.957864  301351 local.go:42] ⚙️ /home/ubuntu/go/src/k8s.io/kops/.build/dist/linux/amd64/kops create cluster --name amd64.k8s.local --cloud gce --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.29.0-alpha.1.62+622509830c1038 --ssh-public-key  --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=ubuntu-os-cloud/ubuntu-2204-jammy-v20230908 --channel=alpha --zones=us-central1-a --node-count=2 --admin-access 0.0.0.0/0 --master-count 1 --master-volume-size 48 --node-volume-size 48 --kubernetes-feature-gates +AllAlpha,-InTreePluginGCEUnregister,+DisableCloudProviders,+DisableKubeletCloudCredentialProviders --master-size e2-standard-2 --node-size e2-standard-2 --project borg-env --gce-service-account default --networking kubenet --set spec.kubeAPIServer.enableAdmissionPlugins=NamespaceLifecycle --set spec.kubeAPIServer.enableAdmissionPlugins=LimitRanger --set spec.kubeAPIServer.enableAdmissionPlugins=ServiceAccount --set spec.kubeAPIServer.enableAdmissionPlugins=PersistentVolumeLabel --set spec.kubeAPIServer.enableAdmissionPlugins=DefaultStorageClass --set spec.kubeAPIServer.enableAdmissionPlugins=DefaultTolerationSeconds --set spec.kubeAPIServer.enableAdmissionPlugins=NodeRestriction --set spec.kubeAPIServer.enableAdmissionPlugins=Priority --set spec.kubeAPIServer.enableAdmissionPlugins=StorageObjectInUseProtection --set spec.kubeAPIServer.enableAdmissionPlugins=PersistentVolumeClaimResize --set spec.kubeAPIServer.enableAdmissionPlugins=RuntimeClass --set spec.kubeAPIServer.enableAdmissionPlugins=MutatingAdmissionWebhook --set spec.kubeAPIServer.enableAdmissionPlugins=ValidatingAdmissionWebhook --set spec.kubeAPIServer.enableAdmissionPlugins=ResourceQuota --set spec.kubeAPIServer.runtimeConfig=api/all=true,extensions/v1beta1=true,scheduling.k8s.io/v1alpha1=true --set spec.kubeAPIServer.enableAggregatorRouting=true --set spec.kubeAPIServer.auditLogPath=/var/log/kube-apiserver-audit.log --set spec.kubeAPIServer.auditLogMaxSize=2000000000 --set spec.kubeAPIServer.logLevel=4
Flag --master-count has been deprecated, use --control-plane-count instead
Flag --master-volume-size has been deprecated, use --control-plane-volume-size instead
Flag --master-size has been deprecated, use --control-plane-size instead
I1001 14:57:03.492401  305295 new_cluster.go:581] VMs will be configured to use specified Service Account: default
I1001 14:57:03.492504  305295 new_cluster.go:1404] Cloud Provider ID: "gce"
Error: field extensions/v1beta1 not found in *Cluster

[hakman]

@upodroid see #15989

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from hakman. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[upodroid]

/retest

[upodroid]

/test pull-kops-e2e-aws-dns-none
/test pull-kops-e2e-gce-dns-none

testing if dns=none is worth it for e2e tests

[hakman]

testing if dns=none is worth it for e2e tests

dns=none is probably the best approach going forward for tests

[hakman]

#16006 should fix dns=none.
I will add a pre-submit to make sure it doesn't get broken again tomorrow.

[k8s-ci-robot]

PR needs rebase.

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.

[k8s-ci-robot]

@upodroid: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kops-e2e-aws-dns-none	eb4b274	link	true	/test pull-kops-e2e-aws-dns-none
pull-kops-kubernetes-e2e-ubuntu-gce-build	eb4b274	link	true	/test pull-kops-kubernetes-e2e-ubuntu-gce-build
pull-kops-verify-hashes	eb4b274	link	true	/test pull-kops-verify-hashes

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closed this PR.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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-sigs/prow repository.