Change:
cluster/cloudcfg.sh list /pods ``` <del> You should see a single redis master pod.  It will also display the machine that the pod is running on.  If you ssh to that machine, you can run </del> <ins> You'll see a single redis master pod. It will also display the machine that the pod is running on. ```javascript Using master: kubernetes-master (external IP: 1.2.3.4) { "kind": "cluster#podList", "items": [ { "id": "redis-master-2", "labels": { "name": "redis-master" }, "desiredState": { "manifest": { "version": "", "volumes": null, "containers": [ { "name": "master", "image": "dockerfile/redis", "ports": [ { "hostPort": 6379, "containerPort": 6379 } ] } ] } }, "currentState": { "manifest": { "version": "", "volumes": null, "containers": null }, "host": "kubernetes-minion-3.c.{project-id}.internal" } } ] } ``` If you ssh to that machine, you can run `docker ps` to see the actual pod: </ins> ```shell <del> sudo docker ps </del> <ins> $ gcloud compute ssh kubernetes-minion-3 --zone us-central1-b $ sudo docker ps me@kubernetes-minion-3:~$ sudo docker ps CONTAINER ID  IMAGE  COMMAND  CREATED  STATUS  PORTS  NAMES 417ab993cdf8  dockerfile/redis:latest  redis-server /etc/re  8 minutes ago Up 8 minutes  0.0.0.0:6379->6379/tcp  master--redis_-_master_-_2--6b944b49 </ins> ``` <del> And see the actual pod.  (Note that initial `docker pull` may take a few minutes, depending on network conditions.) </del> <ins> (Note that initial `docker pull` may take a few minutes, depending on network conditions.) </ins> ### Step Two: Turn up the master service. <del> A Kubernetes 'service' is a named load balancer that proxies traffic to one or more containers.  The services in a Kubernetes cluster are discoverable inside other containers via environment variables.  Services find the containers to load balance based on pod labels.  The pod that you created in Step One has the label `name=redis-master`, so the corresponding service is defined by that label.  Create a file named `redis-master-service.json` that contains: </del> <ins> A Kubernetes 'service' is a named load balancer that proxies traffic to one or more containers. The services in a Kubernetes cluster are discoverable inside other containers via environment variables. Services find the containers to load balance based on pod labels. </ins> <del> ```javascript </del> <ins> The pod that you created in Step One has the label `name=redis-master`, so the corresponding service is defined by that label.  Create a file named `redis-master-service.json` that contains: ```js </ins> { "id": "redismaster", "port": 10000,

Discussion:
<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security related, please disclose it privately via --What happened: I am running an admission webhook using If there it has been hours since the last mutating request to the webhook, then the next mutating request will take many seconds to be processed. This may even take long enough to have the request time out. What you expected to happen: A request takes approximately the same amount of time to be processed regardless of how long it has been since the last request. How to reproduce it (as minimally and precisely as possible): Create an API server for handling a new API group. Wait a couple hours. Send a CREATE request to the API server. Observe that the CREATE request takes a few seconds to complete. Anything else we need to know?: This is the offending code. It must loop through once for every second since the last request. Environment: Kubernetes version (use ): 1.19.0
/sig api-machinery
I thought we'd already merged a fix for this from before the release?
I assume that the fix was supposed to be From my understanding, those changes only are in effect if the apiserver is running with priority and fairness enabled. In my situation, I do not have that enabled.
Ack, if we have the problem in both places we need the fix in both places :)
/triage accepted
I think we have fixed this in , do you guys agree?