### What happened?

Most services access the APIServer through the service of the ClusterIP type. The relationship between the service and the endpoints is created by the APIServer , and then the iptables routing rule maintained by kube-proxy. When the APIServer is restarted, the routing rule cannot be updated quickly. A large amount of service traffic is received. CPU resources are limited and the CPU usage is high. As a result, the APIServer health check timeout and then the APIServer exits automatically. As a result, the service is unavailable.

### What did you expect to happen?

Before the APIServer is started successfully, a filter is added to the ingress to control the incoming traffic, ensuring that the APIServer can be started successfully and enhancing the APIServer reliability.

### How can we reproduce it (as minimally and precisely as possible)?

When the APIServer is started, a large number of requests are sent to the APIServer. As a result, the CPU is overloaded and the APIServer health check times out.

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>

```[tasklist]
### Tasks
```

The APIServer health check failed. As a result, the APIServer automatically exits and APIServer unavailable.
This is a GitHub Issue
repo:kubernetes
owner:kubernetes
Title : The APIServer health check failed. As a result, the APIServer automatically exits and APIServer unavailable.
Issue date:

--- start body ---
### What happened?

Most services access the APIServer through the service of the ClusterIP type. The relationship between the service and the endpoints is created by the APIServer , and then the iptables routing rule maintained by kube-proxy. When the APIServer is restarted, the routing rule cannot be updated quickly. A large amount of service traffic is received. CPU resources are limited and the CPU usage is high. As a result, the APIServer health check timeout and then the APIServer exits automatically. As a result, the service is unavailable.

### What did you expect to happen?

Before the APIServer is started successfully, a filter is added to the ingress to control the incoming traffic, ensuring that the APIServer can be started successfully and enhancing the APIServer reliability.

### How can we reproduce it (as minimally and precisely as possible)?

When the APIServer is started, a large number of requests are sent to the APIServer. As a result, the CPU is overloaded and the APIServer health check times out.

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>

```[tasklist]
### Tasks
```

--- end body ---
