}
				}
			}
			s.RUnlock()

			resyncTimer.Reset(resyncTimeInterval)
		case <-ctx.Done():
			// server could be restarting - need
			// to exit immediately
			return
		}
	}
}

const (
	resyncWorkerCnt        = 10 // limit of number of bucket resyncs is progress at any given time

- `kubectl diff` now returns 1 only on diff finding changes, and >1 on kubectl errors. The "exit status code 1" message has also been muted. ([#87437](https://github.com/kubernetes/kubernetes/pull/87437), [@apelisse](https://github.com/apelisse)) [SIG CLI and Testing]

## Dependencies

HSPLokio/AsyncTimeout$source$1;->close()V
HSPLokio/AsyncTimeout$source$1;->read(Lokio/Buffer;J)J
HSPLokio/AsyncTimeout;-><clinit>()V
HSPLokio/AsyncTimeout;-><init>()V
HSPLokio/AsyncTimeout;->enter()V
HSPLokio/AsyncTimeout;->exit()Z
HSPLokio/Buffer;-><init>()V
HSPLokio/Buffer;->exhausted()Z
HSPLokio/Buffer;->getByte(J)B
HSPLokio/Buffer;->indexOfElement(Lokio/ByteString;)J
HSPLokio/Buffer;->rangeEquals(JLokio/ByteString;)Z

containers can be added to running pods for purposes such as debugging, similar to how `kubectl exec` runs a process in an existing container. Also like `kubectl exec`, no resources are reserved for ephemeral containers and they are not restarted when they exit. Note that container namespace targeting is not yet implemented, so [process namespace sharing](https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/) must be enabled to view process from other containers in the pod. ([...

“kc@ žIµŒöñ`« ‰(»óºòF' •¬Oå±S ×È:25Z;%’É@g P§² ¾Y; 'a’ õMŽ >P!Éx r CSlpÇ3·dá~òìKTÆmQBë5£;ôß2ýôö¯ì8/p£·‚ñIÉ™O» ' T ¨`^ ³ ƒceQ±*2ÎçÎ¡Ñ G–LÍTNk#Ô H±,-~Øa8 ŒKIÍó—VÆ Îeõµ#ž€Ç2¿E5]zݲC¢"ˆÁ ’N¯Œ _Þ´¾Aá"¥x:¤hþ¤‰ Ï„Ñ¥ ‡ ¤¹{ÙTöë¼zµßɲ¨.­ûhcƒ"¹x÷ªno7¾O} ”í`‚ÒP%è¸ÖéXì uøoûv{ú\ÌÃÐ,7 Á3 è’6‰”…‹1o-L ÞâãÒº¢ jó ðý†Jçö ÿ` øåI=˜ê:W ï°‡ºT³ ¦€O8Kù ïÇÛ<Ð} 4ýÚøÚûÏ: J* ‹÷™í€€èƒ”Ávà #ã〠¢eìB\Ä t²û£¡Ð x® ?ß•sS=dHrèæ4p íŒ6” gþŒ°Ëí÷/8Êò ýÎzŽçÙ- ¬‹ © £ ôìü ¡ S&cé’¹v¼\-g=âàÝ 2Jëm ;¯0²Gñø×ôÈŒ_T Ȫ Þ r<‹@N›¡GÞ >ÐÛ ‘& tdo k '°l1;¼oãÓà’ƒœüè¤9*`zÈÍM‘...

- Fixed bug where a nonzero exit code was returned when initializing zsh completion even though zsh completion was successfully initialized ([#88165](https://github.com/kubernetes/kubernetes/pull/88165), [@brianpursley](https://github.com/brianpursley)) [SIG CLI]

- Increased log level to 2 for IPVS graceful termination ([#78395](https://github.com/kubernetes/kubernetes/pull/78395), [@andrewsykim](https://github.com/andrewsykim))
- kube-proxy: os exit when CleanupAndExit is set to true ([#76732](https://github.com/kubernetes/kubernetes/pull/76732), [@JieJhih](https://github.com/JieJhih))

- The `kubectl patch` command no longer exits with exit code 1 when a redundant patch results in a no-op ([#66725](https://github.com/kubernetes/kubernetes/pull/66725), [@juanvallejo](https://github.com/juanvallejo))

- Run kubelet, when there is an error exit, print the error log ([#110917](https://github.com/kubernetes/kubernetes/pull/110917), [@yangjunmyfm192085](https://github.com/yangjunmyfm192085)) [SIG Node]

## Dependencies

### Added
_Nothing has changed._

- Fixed a bug that `kubectl create configmap` always returns zero exit code when failed. ([#101780](https://github.com/kubernetes/kubernetes/pull/101780), [@nak3](https://github.com/nak3)) [SIG CLI]