• v1.30.0
  • Downloads for v1.30.0
    • Source Code
    • Client Binaries
    • Server Binaries
    • Node Binaries
    • Container Images
  • Changelog since v1.29.0
  • Changes by Kind
    • Deprecation
    • API Change
    • Feature
    • Documentation
    • Failing Test
    • Bug or Regression
    • Other (Cleanup or Flake)
    • Uncategorized
  • Dependencies
    • Added
    • Changed
    • Removed
• v1.30.0-rc.2
  • Downloads for v1.30.0-rc.2
    • Source Code
    • Client Binaries
    • Server Binaries
    • Node Binaries
    • Container Images
  • Changelog since v1.30.0-rc.1
  • Changes by Kind
    • Feature
    • Bug or Regression
  • Dependencies
    • Added
    • Changed
    • Removed
• v1.30.0-rc.1
  • Downloads for v1.30.0-rc.1
    • Source Code
    • Client Binaries
    • Server Binaries
    • Node Binaries
    • Container Images
  • Changelog since v1.30.0-rc.0
  • Changes by Kind
    • Bug or Regression
  • Dependencies
    • Added
    • Changed
    • Removed
• v1.30.0-rc.0
  • Downloads for v1.30.0-rc.0
    • Source Code
    • Client Binaries
    • Server Binaries
    • Node Binaries
    • Container Images
  • Changelog since v1.30.0-beta.0
  • Changes by Kind
    • Failing Test
    • Bug or Regression
  • Dependencies
    • Added
    • Changed
    • Removed
• v1.30.0-beta.0
  • Downloads for v1.30.0-beta.0
    • Source Code
    • Client Binaries
    • Server Binaries
    • Node Binaries
    • Container Images
  • Changelog since v1.30.0-alpha.3
  • Changes by Kind
    • API Change
    • Feature
    • Bug or Regression
    • Other (Cleanup or Flake)
  • Dependencies
    • Added
    • Changed
    • Removed
• v1.30.0-alpha.3
  • Downloads for v1.30.0-alpha.3
    • Source Code
    • Client Binaries
    • Server Binaries
    • Node Binaries
    • Container Images
  • Changelog since v1.30.0-alpha.2
  • Changes by Kind
    • API Change
    • Feature
    • Documentation
    • Bug or Regression
    • Other (Cleanup or Flake)
  • Dependencies
    • Added
    • Changed
    • Removed
• v1.30.0-alpha.2
  • Downloads for v1.30.0-alpha.2
    • Source Code
    • Client Binaries
    • Server Binaries
    • Node Binaries
    • Container Images
  • Changelog since v1.30.0-alpha.1
  • Changes by Kind
    • Deprecation
    • API Change
    • Feature
    • Bug or Regression
    • Other (Cleanup or Flake)
  • Dependencies
    • Added
    • Changed
    • Removed
• v1.30.0-alpha.1
  • Downloads for v1.30.0-alpha.1
    • Source Code
    • Client Binaries
    • Server Binaries
    • Node Binaries
    • Container Images
  • Changelog since v1.29.0
  • Changes by Kind
    • Deprecation
    • API Change
    • Feature
    • Documentation
    • Bug or Regression
    • Other (Cleanup or Flake)
  • Dependencies
    • Added
    • Changed
    • Removed

Documentation

All container images are available as manifest lists and support the described architectures. It is also possible to pull a specific architecture directly by adding the "-$ARCH" suffix to the container image name.

• kubectl: Removed the deprecated flag prune-whitelist for apply. Please use the flag prune-allowlist instead. (#120246, @pacoxu)
• The deprecated SecurityContextDeny admission plugin, which has been deprecated since v1.27, has been removed. It is recommended to use the Pod Security Admission plugin instead, which has been available since v1.25. Refer to the Kubernetes documentation for more information. (#122612, @mtardy)

• Added (alpha) support for the managedBy field on Jobs. Jobs with a custom value of this field - any value other than kubernetes.io/job-controller - were skipped by the job controller, and their reconciliation was delegated to an external controller, indicated by the value of the field. Jobs that didn't have this field at all, or where the field value was the reserved string kubernetes.io/job-controller, were reconciled by the built-in job controller. (#123273, @mimowo)

• Added alpha-level support for the SuccessPolicy in Jobs. (#123412, @tenzen-y)

• Added the CEL library for IP Addresses and CIDRs. This was made available for use starting from version 1.31. (#121912, @JoelSpeed)

• Allowed container runtimes to fix an image garbage collection bug by adding an image_id field to the CRI Container message. (#123508, @saschagrunert)

• Dynamic Resource Allocation: DRA drivers can now use "structured parameters" to let the scheduler handle claim allocation. (#123516, @pohly)

• Fixed accidental enablement of the new alpha optionalOldSelf API field in CustomResourceDefinition validation rules, which should only have been allowed to be set when the CRDValidationRatcheting feature gate is enabled. (#122329, @jpbetz)

• Implemented the prescore extension point for the volumeBinding plugin. It now returns skip if it doesn't do anything in Score. (#115768, @AxeZhan)

• Kubelet would fail if NodeSwap was used with LimitedSwap and cgroupv1 node. (#123738, @kannon92)

• Promoted AdmissionWebhookMatchConditions to GA. The feature is now stable, and the feature gate is now locked to default. (#123560, @ivelichkovich)

• Structured Authentication Configuration now supports DiscoveryURL. If specified, discoveryURL overrides the URL used to fetch discovery information. This is for scenarios where the well-known and jwks endpoints are hosted at a different location than the issuer (such as locally in the cluster). (#123527, @aramase)

• The StorageVersionMigration API, previously available as a Custom Resource Definition (CRD), is now a built-in API in Kubernetes. (#123344, @nilekhc)

• When configuring a JWT authenticator:

  If username.expression used 'claims.email', then 'claims.email_verified' must have been used in username.expression or extra[*].valueExpression or claimValidationRules[*].expression. An example claim validation rule expression that matches the validation automatically applied when username.claim is set to 'email' is 'claims.?email_verified.orValue(true)'. (#123737, @enj)

• readOnly volumes now support recursive read-only mounts for kernel versions >= 5.12." (#123180, @AkihiroSuda)

• cri-api: Implemented KEP-3857: Recursive Read-only (RRO) mounts. (#123272, @AkihiroSuda)

• kube-apiserver: the AuthenticationConfiguration type accepted in --authentication-config files has been promoted to apiserver.config.k8s.io/v1beta1. (#123696, @aramase)

• kubelet allowed specifying a custom root directory for pod logs (instead of the default /var/log/pods) using the podLogsDir key in kubelet configuration. (#112957, @mxpv)

• resource.k8s.io/ResourceClaim (alpha API): The strategic merge patch strategy for the status.reservedFor array was changed so that a strategic-merge-patch can now add individual entries. This change may break clients using strategic merge patch to update status, which rely on the previous behavior (replacing the entire array). (#122276, @pohly)

• Added a CBOR implementation of runtime.Serializer. Until CBOR graduates to Alpha, API servers will refuse to start if configured with CBOR support. (#122881, @benluddy)

• Added a alpha feature, behind the RelaxedEnvironmentVariableValidation feature gate. When that gate is enabled, Kubernetes allows almost all printable ASCII characters to be used in the names of environment variables for containers in Pods. (#123385, @HirazawaUi)

• Added a new (alpha) field, trafficDistribution, to the Service spec to express preferences for traffic distribution to endpoints. Enabled through the ServiceTrafficDistribution feature gate. (#123487, @gauravkghildiyal)

• Added audienceMatchPolicy field to AuthenticationConfiguration and support for configuring multiple audiences. The "audienceMatchPolicy" can be empty (or unset) when a single audience is specified in the "audiences" field. The "audienceMatchPolicy" must be set to "MatchAny" when multiple audiences are specified in the "audiences" field. (#123165, @aramase)

• Added consistent vanity import to files and provided tooling for verifying and updating them. (#120642, @jcchavezs)

• Added the disable-force-detach CLI option for kube-controller-manager. By default, it's set to false. When enabled, it prevents force detaching volumes based on maximum unmount time and node status. If activated, the non-graceful node shutdown feature must be used to recover from node failure. Additionally, if a pod needs to be forcibly terminated at the risk of corruption, the appropriate VolumeAttachment object must be deleted. (#120344, @rohitssingh)

• Added to MutableFeatureGate the ability to override the default setting of feature gates, to allow default-enabling a feature on a component-by-component basis instead of for all affected components simultaneously. (#122647, @benluddy)

• Aggregated discovery supports both v2beta1 and v2 types and feature is promoted to GA. (#122882, @Jefftree)

• Alpha support for field selectors on custom resources has been added. With the CustomResourceFieldSelectors feature gate enabled, the CustomResourceDefinition API now allows specifying selectableFields. Listing a field there enables filtering custom resources for that CustomResourceDefinition in list or watch requests. (#122717, @jpbetz)

• AppArmor profiles can now be configured through fields on the PodSecurityContext and container SecurityContext. The beta AppArmor annotations are deprecated, and AppArmor status is no longer included in the node ready condition. (#123435, @tallclair)

• Contextual logging is now in beta and enabled by default. Check out the KEP and official documentation for more details. (#122589, @pohly)

• Enabled concurrent log rotation in kubelet. You can now configure the maximum number of concurrent rotations with the containerLogMaxWorkers setting, and adjust the monitoring interval with containerLogMonitorInterval. (#114301, @harshanarayana)

• Graduated pod scheduling gates to general availability. The PodSchedulingReadiness feature gate no longer has any effect, and the .spec.schedulingGates field is always available within the Pod and PodTemplate APIs. (#123575, @Huang-Wei)

• Graduated support for minDomains in pod topology spread constraints, to general availability. The MinDomainsInPodTopologySpread feature gate no longer has any effect, and the field is always available within the Pod and PodTemplate APIs. (#123481, @sanposhiho)

• In kubelet configuration, the .memorySwap.swapBehavior field now accepts a new value NoSwap, which becomes the default if unspecified. The previously accepted UnlimitedSwap value has been dropped. (#122745, @kannon92)

• Kube-apiserver: the AuthorizationConfiguration type accepted in --authorization-config files has been promoted to apiserver.config.k8s.io/v1beta1. (#123640, @liggitt)

• OIDC authentication will now fail if the username asserted based on a CEL expression config is the empty string. Previously the request would be authenticated with the username set to the empty string. (#123568, @enj)

• Removed note that hostAliases are not supported on hostNetwork Pods from the PodSpec API. The feature has been supported since v1.8. (#122422, @neolit123)

• Structured Authentication Configuration now supports configuring multiple JWT authenticators. The maximum allowed JWT authenticators in the authentication configuration is 64. (#123431, @aramase)

• Text logging in Kubernetes components now uses textlogger. The same split streams of info and error log entries with buffering of info entries is now also supported for text output (off by default, alpha feature). Previously, this was only supported for JSON. Performance is better also without split streams. (#114672, @pohly)

• The API server now detects and fails on startup if there are conflicting issuers between JWT authenticators and service account configurations. Previously, such configurations would run but could be inconsistently effective depending on the credential. (#123561, @enj)

• The JWT authenticator configuration set via the --authentication-config flag is now dynamically reloaded as the file changes on disk. (#123525, @enj)

• The StructuredAuthenticationConfiguration feature is now beta and enabled. (#123719, @enj)

• The kube_codegen tool now ignores the vendor folder during code generation. (#122729, @jparrill)

• The kubernetes repo now uses Go workspaces. This should not impact end users at all, but does have impact for developers of downstream projects. Switching to workspaces caused some breaking changes in the flags to the various k8s.io/code-generator tools. Downstream consumers should look at staging/src/k8s.io/code-generator/kube_codegen.sh to see the changes. (#123529, @thockin)

• Updated an audit annotation key used by the …/serviceaccounts/<name>/token resource handler. The annotation used to persist the issued credential identifier is now authentication.kubernetes.io/issued-credential-id. (#123098, @munnerz) [SIG Auth]

• Users are now allowed to mutate FSGroupPolicy and PodInfoOnMount in CSIDriver.Spec. (#116209, @haoruan)

• ValidatingAdmissionPolicy was promoted to GA and will be enabled by default. (#123405, @cici37)

• When scheduling a mix of pods using ResourceClaims and others that don't, scheduling a pod with ResourceClaims has a lower impact on scheduling latency. (#121876, @pohly)

• When working with client-go events, it's now recommended to use NewEventBroadcasterAdapterWithContext instead of NewEventBroadcasterAdapter if contextual logging support is needed. (#122142, @pohly)

• Added Timezone column in the output of the 'kubectl get cronjob' command. (#122231, @ardaguclu)
• Added WatchListClient feature gate to client-go. When enabled, it allows the client to receive a stream of individual items instead of chunking from the server. (#122571, @p0lyn0mial)
• Added the apiserver_watch_cache_read_wait metric to measure the watch cache impact on request latency. (#123190, @padlar)
• Allowed scheduling framework plugins that implement io.Closer to be gracefully closed. (#122498, @Gekko0114)
• Bumped cAdvisor to v0.49.0. (#123599, @bobbypage)
• Changed --nodeport-addresses behavior to default to "primary node IP(s) only" rather than "all node IPs". (#122724, @nayihz)
• In the Pod API, setting the alpha procMount field to Unmasked in a container now required setting spec.hostUsers=false as well. (#123520, @haircommander)
• Informers now supports adding Indexers after the informer starts. (#117046, @howardjohn)
• Printed more information when kubectl describe a VolumeAttributesClass. (#122640, @carlory)
• Promoted the CRDValidationRatcheting feature gate to beta and made it enabled by default. (#121461, @alexzielenski)
• Scheduler now skips the NodeAffinity Score plugin when it has nothing to do with a Pod. You might have noticed an increase in the metric plugin_execution_duration_seconds for extension_point=score and plugin=NodeAffinity, because the plugin only runs when it's relevant. (#117024, @sanposhiho)
• Some interfaces' signatures in the scheduler were updated: - PluginsRunner: used NodeInfo in RunPreScorePlugins and RunScorePlugins. - PreScorePlugin: used NodeInfo in PreScore. - Extender: used NodeInfo in Filter and Prioritize. (#121954, @AxeZhan)
• The watch cache now waits until it is at least as fresh as the given requestedWatchRV if sendInitialEvents was requested. (#122830, @p0lyn0mial)
• Updated ImageGCMaxAge behavior in the kubelet to wait the MaxAge duration after the kubelet has restarted before garbage collecting. (#123343, @haircommander)
• Updated distroless-iptables to v0.5.0, debian-base to bookworm-v1.0.1, and setcap to bookworm-v1.0.1. (#123170, @cpanato)
• NewVolumeManagerReconstruction feature is now GA. (#123442, @jsafrane)
• kubectl describe: Added Suspend to job and Node-Selectors and Tolerations to pod template output. (#122618, @ivanvc)
• kubectl get job now displays the status for the listed jobs. (#123226, @ivanvc)
• etcd: Built image for v3.5.11. (#122233, @mzaian)
• kube-apiserver now reloads the --authorization-config file when it changes. Reloads increment the apiserver_authorization_config_controller_automatic_reload_last_timestamp_seconds timestamp metric, with status="success" for successful reloads and status="failed" for failed reloads. Failed reloads keep using the previously loaded authorization configuration. (#121946, @liggitt)
• kube-apiserver now reported the following metrics for authorization webhook match conditions: - apiserver_authorization_match_condition_evaluation_errors_total counter metric labeled by authorizer type and name - apiserver_authorization_match_condition_exclusions_total counter metric labeled by authorizer type and name - apiserver_authorization_match_condition_evaluation_seconds histogram metric labeled by authorizer type and name. (#123611, @ritazh)
• kube-apiserver: JWT authenticator now reports the following metrics: - apiserver_authentication_config_controller_automatic_reloads_total - apiserver_authentication_config_controller_automatic_reload_last_timestamp_seconds (#123793, @aramase)
• kube-apiserver: The StructuredAuthorizationConfiguration feature gate has been promoted to beta and now allows the use of the --authorization-configuration flag. (#123641, @liggitt)
• kube-scheduler implemented scheduling hints for the NodeUnschedulable plugin. The scheduling hints allowed the scheduler to only retry scheduling a Pod that had been previously rejected by the NodeSchedulable plugin if a new Node or a Node update had set .spec.unschedulable to false. (#122334, @carlory)
• kubeadm: Added better handling of errors during unmount when calling kubeadm reset. When failing to unmount directories under /var/run/kubelet, kubeadm will now throw an error instead of showing a warning and continuing to clean up said directory. In such situations, it is better for you to inspect the problem and resolve it manually. Then, you can call kubeadm reset again to complete the cleanup. (#122530, @neolit123)
• kubeadm: Added support for machine-readable output with -o yaml and -o json to the command kubeadm certs check-expiration. This change is introduced in a new API: kind: CertificateExpirationInfo apiVersion: output.kubeadm.k8s.io/v1alpha3 The existing non-structured formatting is preserved. The output API version v1alpha2 is now deprecated and will be removed in a future release. Please migrate to using v1alpha3. (#123372, @carlory)
• kubeadm: added the WaitForAllControlPlaneComponents feature gate. It could be used to tell kubeadm to wait for all control plane components to be ready when running "kubeadm init" or "kubeadm join --control-plane". Previously, kubeadm only waited for the kube-apiserver. The "kubeadm join" workflow now includes a new experimental phase called "wait-control-plane". This phase was marked as non-experimental when WaitForAllControlPlaneComponents became GA. Accordingly, a "kubeadm init" phase "wait-control-plane" was also available once WaitForAllControlPlaneComponents became GA. These phases could be skipped if the user preferred not to wait for the control plane components. (#123341, @neolit123)
• kubectl port-forward over websockets (tunneling SPDY) can now be enabled using an Alpha feature flag environment variable: KUBECTL_PORT_FORWARD_WEBSOCKETS=true. The API Server being communicated to must also have an Alpha feature flag enabled: PortForwardWebsockets. (#123413, @seans3)
• A new flag called custom has been introduced in kubectl debug, allowing users to customize pre-defined profiles. (#120346, @ardaguclu)
• A new kubelet metric image_pull_duration_seconds was added. The metric tracks the duration (in seconds) it takes for an image to be pulled, including the time spent in the waiting queue of image puller. The metric is broken down by bucketed image size. (#121719, @ruiwen-zhao)
• A new metric lifecycle_handler_sleep_terminated_total is added to record how many times LifecycleHandler sleep got unexpectedly terminated. (#122456, @AxeZhan)
• Added client-go support for upgrading subresource fields from client-side to server-side management. (#123484, @erikgb)
• Added exec-interactive-mode and exec-provide-cluster-info flags in kubectl config set-credentials command. (#122023, @ardaguclu)
• Added process_start_time_seconds to /metrics/slis endpoint of all components. (#122750, @richabanker)
• Added a "reason" field to the "image_garbage_collected_total" metric, allowing administrators to differentiate between images that were collected for reasons "age" vs "space". (#123345, @haircommander)
• Added a new metric apiserver_encryption_config_controller_automatic_reloads_total to measure the total number of API server encryption configuration reload successes and failures. This metric now contains the status label with a value that is either success or failure. Deprecated the metrics apiserver_encryption_config_controller_automatic_reload_success_total and apiserver_encryption_config_controller_automatic_reload_failure_total. Please use apiserver_encryption_config_controller_automatic_reloads_total instead. (#123179, @aramase)
• Added feature gate MutatingAdmissionPolicy for enabling mutation policy in admission chain. (#123425, @cici37)
• Added kubelet metrics to track the memory manager allocation and pinning. (#121778, @Tal-or)
• Added the access_mode label to volume_manager_selinux_* metrics. (#123667, @jsafrane)
• Enhanced cloud provider integrations to support optional, per-Node custom labels that can be supplied and applied to Nodes by the node controller. These extra labels will only be applied where the cloud provider integration supports this feature. (#123223, @mmerkes)
• Graduated "Forensic Container Checkpointing" (KEP #2008) from Alpha to Beta. (#123215, @adrianreber)
• Graduated HorizontalPodAutoscaler support for per-container metrics to stable. (#123482, @sanposhiho)
• Graduated support for passing dual-stack kubelet --node-ip values when using a cloud provider. The feature is now GA, and the CloudDualStackNodeIPs feature gate is always enabled. (#123134, @danwinship)
• In the PriorityLevelConfiguration object, the nominalConcurrencyShares field now accepts a zero value in both the flowcontrol.apiserver.k8s.io/v1 and flowcontrol.apiserver.k8s.io/v1beta3 APIs. (#123001, @tkashem)
• Introduced a feature gate mechanism to client-go. Depending on the actual implementation, users can control features via environmental variables or command line options. (#122555, @p0lyn0mial)
• Introduced a new alpha feature gate, SELinuxMount, which can now be enabled to accelerate SELinux relabeling. (#123157, @jsafrane)
• Kube-apiserver now reports latency metric for JWT authenticator authenticate token decisions in the apiserver_authentication_jwt_authenticator_latency_seconds metric, labeled by jwtIssuer hash and result. (#123225, @aramase)
• Kube-apiserver now reports metrics for authorization decisions in the apiserver_authorization_decisions_total metric, labeled by authorizer type, name, and decision. (#123333, @liggitt)
• Kube-apiserver: Authorization webhooks now report the following metrics:
  • apiserver_authorization_webhook_evaluations_total
  • apiserver_authorization_webhook_duration_seconds
  • apiserver_authorization_webhook_evaluations_fail_open_total (#123639, @liggitt)
• Kube-controller-manager: increased the global level for broadcaster's logging to 3 so that users can ignore event messages by lowering the logging level. It reduces information noise. (#122293, @mengjiao-liu)
• Kube-scheduler implemented scheduling hints for the NodeAffinity plugin. The scheduling hints allowed the scheduler to only retry scheduling a Pod that had been previously rejected by the NodeAffinity plugin if a new Node or a Node update matched the Pod's node affinity. (#122309, @carlory)
• Kube-scheduler implemented scheduling hints for the NodeResourceFit plugin. The scheduling hints allowed the scheduler to only retry scheduling a Pod that had been previously rejected by the NodeResourceFit plugin if a new Node or a Node update matched the Pod's resource requirements or if an old pod update or delete matched the Pod's resource requirements. (#119177, @carlory)
• Kube-scheduler now retries scheduling Pods rejected by the PodTopologySpread plugin when related Pods are created, deleted, updated, or when a node matches the specified topologyKey. (#122195, @nayihz)
• Kubeadm now prints all the kubelets and nodes that need to be upgraded when running "upgrade plan". (#123578, @carlory)
• Kubectl debug now includes the sysadmin profile. (#119200, @eiffel-fl)
• Kubelet now supports configuring the IDs used to create user namespaces. (#123593, @giuseppe)
• Kubernetes is now built with Go 1.21.6. (#122705, @cpanato)
• Kubernetes is now built with Go 1.22.1. (#123750, @cpanato)
• Kubernetes is now built with Go 1.22. (#123217, @cpanato)
• Kubernetes is now built with go 1.22rc2. (#122889, @cpanato)
• LoadBalancerIPMode feature is now marked as Beta. (#123418, @rikatz)
• Node information is now embedded into Pod-bound service account tokens as additional metadata. The 'JTI' field is set in issued service account tokens, and this information is embedded as authentication.kubernetes.io/credential-id in the user's ExtraInfo. (#123135, @munnerz)
• Node podresources API now includes init containers with containerRestartPolicy of Always when SidecarContainers feature is enabled. (#120718, @gjkim42)
• Promoted KubeProxyDrainingTerminatingNodes to Beta. (#122914, @alexanderConstantinescu)
• Promoted feature gate StableLoadBalancerNodeSet to GA . (#122961, @alexanderConstantinescu)
• Promoted the ImageMaximumGCAge feature to beta. (#123424, @haircommander)
• Promoted the status.hostIPs field for Pods to general availability. The PodHostIPs feature gate no longer has any effect, and the status.hostIPs field is always available within the Pod API. (#122870, @wzshiming)
• RemoteCommand feature gates for kubectl exec, cp, and attach over WebSockets are now enabled by default (Beta):
  • Server-side feature gate: TranslateStreamCloseWebsocketRequests
  • Client-side (kubectl) feature gate: KUBECTL_REMOTE_COMMAND_WEBSOCKETS
  • To disable RemoteCommand over WebSockets for kubectl, the environment variable feature gate must be explicitly set to false: KUBECTL_REMOTE_COMMAND_WEBSOCKETS=false. (#123281, @seans3)
• Revised node selection based on container image location. The kube-scheduler now considers whether nodes have the required images available for init containers, and for sidecar containers if the cluster has 'SidecarContainers' enabled. (#123366, @kerthcet)
• Scheduler extender ignorable option now handles errors for both filter and bind phases. (#122503, @sunbinnnnn)
• The NodeLogQuery feature has been promoted to beta. No functional changes have been made from the alpha version. (#123205, @aravindhp)
• The apiserver.latency.k8s.io/decode-response-object annotation was added to the audit log to record the decoding time. (#121512, @HirazawaUi)
• The drop-in kubelet configuration directory feature has been targeted for Beta. (#122907, @sohankunkerkar)
• The kubelet now rejects creating the pod if hostUserns=false and the CRI runtime does not support user namespaces. (#123216, @giuseppe)
• The scheduler now retries Pods, which are failed by nodevolumelimits due to not found PVCs, only when new PVCs are added. (#121952, @sanposhiho)
• Updated kubedns and nodelocaldns to release version 1.22.28. (#121908, @mzaian)
• Users can now traverse all the pods that are in the scheduler and waiting in the permit stage through method IterateOverWaitingPods. In other words, all waitingPods in scheduler can be obtained from any profiles. Before this commit, each profile could only obtain waitingPods within that profile (#122946, @NoicFank)
• ValidatingAdmissionPolicy now exclude TokenReview, SelfSubjectReview, LocalSubjectAccessReview, and SubjectAccessReview from all versions of authentication.k8s.io and authorization.k8s.io group. (#123543, @jiahuif)
• When a PreFilterResult filters out certain Nodes, the scheduling framework now categorizes them as rejected via UnschedulableAndUnresolvable. Consequently, these nodes are excluded from the candidates for the preemption process. Additionally, this update corrects how the scheduling framework handles the Unschedulable status from PreFilter. Previously, if PreFilter returned Unschedulable, it could lead to an unexpected abortion in the preemption process, which shouldn't occur in the default scheduler but might occur in schedulers with custom plugins. (#119779, @sanposhiho)
• When the RetryGenerateName feature gate is enabled on the kube-apiserver, create requests using generateName are retried automatically by the apiserver when the generated name conflicts with an existing resource name, up to a max limit of 7 retries. This feature is in alpha. (#122887, @jpbetz)
• ValidatingAdmissionPolicy now supports type checking policies that utilize variables. (#123083, @jiahuif)

• Added a new internal metric kubelet_first_network_pod_start_sli_duration_second in the kubelet that allowed developers to understand the source of the latency problems on node startups. (#121720, @aojea)
• A deprecated flag --pod-max-in-unschedulable-pods-duration was initially planned to be removed in v1.26, but we had to change this plan. We found an issue in which Pods can be stuck in the unschedulable pod pool for 5 min, and using this flag is the only workaround for this issue. This issue only could happen if you use custom plugins or if you change plugin set being used in your scheduler via the scheduler config. (#122013, @sanposhiho)
• Modified the error message of unmanagedFatal to enhance clarity while preserving grammatical consistency with unmanagedWarning. This improvement ensures a more understandable prompt for users. (#120159, @Ithrael)

• Reverted the change to "support sharing waitingPods across different scheduler profiles". (#124001, @kerthcet)

• Added imagefs.inodesfree to default EvictionHard settings. (#121834, @vaibhav2107)
• Changed the API server so that for admission webhooks that have a URL matching the hostname 'localhost' or a loopback IP address, the connection supports HTTP/2 where it could be negotiated. (#122558, @linxiulei)
• Fixed CEL estimated cost for expressions that perform operations on the result of map() operations (e.g., .map(...).exists(...) ) to have the correct estimated cost instead of an unbounded cost. (#123562, @jpbetz)
• Fixed a 1.27.0+ regression in kubeadm: The kubelet patch configuration will not be uploaded into the kube-system/kubelet-config ConfigMap anymore. (#123093, @SataQiu)
• Fixed a bug in ValidatingAdmissionPolicy that caused policies using CRD parameters to fail to synchronize. (#123003, @alexzielenski)
• Fixed a non-recursive list returning "resource version too high" error when consistent listing from cache is enabled. (#123674, @serathius)
• Fixed a regression in kube-proxy introduced in version 1.26.0+ to make externalIPs workwith externalTrafficPolicy: Local. (#121919, @uablrek)
• Fixed a regression in migration of in-tree vSphere volumes to the CSI driver introduced in version 1.29.0+. (#122341, @jsafrane)
• Fixed a regression since 1.24 in the scheduling framework when overriding MultiPoint plugins (e.g. default plugins). The incorrect loop logic might have led to a plugin being loaded multiple times, consequently preventing any Pod from being scheduled, which was unexpected. (#122068, @caohe)
• Fixed an issue where AvailableBytes sometimes did not report correctly on WindowsNodes when the PodAndContainerStatsFromCRI feature was enabled. (#122846, @marosset)
• Fixed an issue where mount points could become local without calling NodePublishVolume after node rebooting. (#119923, @cvvz)
• Fixed cleanup of Pod volume mounts when a file was used as a subpath. (#123052, @jsafrane)
• Fixed error handling in EnsureAdminClusterRoleBindingImpl. (#122893, @danwinship)
• Fixed incorrect error logging for syncCronJob. (#122493, @mengjiao-liu)
• Fixed the deprecated version for pod_scheduling_duration_seconds that caused the metric to be hidden by default in 1.29. (#123038, @alculquicondor)
• Fixed the disruption controller's PDB status synchronization to maintain all PDB conditions during an update. (#122056, @dhenkel92)
• Improved scheduler performance when no scoring plugins were defined. (#122058, @aleksandra-malinowska)
• Improved scheduler performance when no scoring plugins were defined. (#122435, @aleksandra-malinowska)
• Improved scheduler performance when no scoring plugins were defined. (#123384, @aleksandra-malinowska)
• In kubeadm, in the new output API 'output.kubeadm.k8s.io/v1alpha3', the UpgradePlan structure that is used when calling 'kubeadm upgrade plan ... -o yaml|json' was modified to include a list of multiple available upgrades. (#123461, @carlory)
• Made decoding etcd's response respect the timeout context. (#121815, @HirazawaUi)
• Previously, the scheduling queue didn't notice any extenders' failures, potentially resulting in missed cluster events and Pods rejected by Extenders being stuck in the unschedulable pod pool for up to 5 minutes in the worst-case scenario. Now, the scheduling queue notices extenders' failures and requeues Pods rejected by Extenders appropriately. (#122022, @sanposhiho)
• QueueingHint implementation for NodeAffinity was reverted because potential scenarios were found where events that make Pods schedulable could be missed. (#122285, @sanposhiho)
• Removed the incorrect warning event FileSystemResizeFailed during pod creation if it uses a readonly volume and the capacity of the volume is greater than or equal to its requested storage. (#122508, @carlory)
• Restored the --verify-only function in code generation wrappers. (#123261, @skitt)
• Reverted the EventedPLEG feature (beta, but disabled by default) back to alpha due to a known issue. (#122697, @pacoxu)
• Used errors.Is() to handle errors returned by LookPath(). (#122600, @lzhecheng)
• kube-proxy: Fixed LoadBalancerSourceRanges not working for nftables mode. (#122614, @tnqn)
• kubeadm: fixed a bug where "kubeadm upgrade plan -o yaml|json" included unneeded output and was missing component config information. (#123492, @carlory)
• Added metric name along with the utilization information when running kubectl get hpa. (#122804, @sreeram-venkitesh)
• Addressed an issue where a JWT authenticator set up via --authentication-config would encounter failures in verifying tokens not signed with RS256. (#123282, @enj)
• DRA: ResourceClaim and PodSchedulingContext status updates no longer allow changing object meta data. (#123730, @pohly)
• Enabled deletion of pods that use raw block volumes on node reboot. (#122211, @gnufied)
• Etcd: Updated to v3.5.11. (#122393, @mzaian)
• Fixed Pod stuck in Terminating because of GenerateUnmapVolumeFunc missing globalUnmapPath when kubelet tries to clean up all volumes that failed reconstruction. (#123032, @carlory)
• Fixed Windows credential provider, cannot find binary. Windows credential provider binary path may have ".exe" suffix so it is better to use LookPath() to support it flexibly. (#120291, @lzhecheng)
• Fixed kubectl explain to show enum for field types if they were defined. (#123023, @ah8ad3)
• Fixed a bug in kubeadm where the --rootfs global flag didn't work with "kubeadm upgrade node" for control plane nodes. (#123077, @neolit123)
• Fixed a bug that an init container with containerRestartPolicy with Always cannot update its state from terminated to non-terminated for the pod with restartPolicy with Never or OnFailure. (#123323, @gjkim42)
• Fixed a bug where kubectl drain would consider a pod as having been deleted if an error occurs while calling the API. (#122574, @brianpursley)
• Fixed a potential data race in DRA with no known real-world implications. (#123222, @pohly)
• Fixed a race condition in the iptables mode of kube-proxy in 1.27 and later that could result in some updates getting lost (e.g., when a service gets a new endpoint, the rules for the new endpoint might not be added until much later). (#122204, @danwinship)
• Fixed a regression in "kubeadm init" where a user-specified --kubeconfig file was being ignored. (#122735, @avorima)
• Fixed a regression in kubectl version 1.29.0 where the --attach flag was not honored. (#122447, @ardaguclu)
• Fixed an error when trying to expand a volume that does not require node expansion. (#123055, @gnufied)
• Fixed an issue calculating total CPU usage reported for Windows nodes. (#122999, @marosset)
• Fixed an issue to ignore unnecessary node events and improve daemonset controller performance. (#121669, @xigang)
• Fixed an issue where the configmap, secret, projected, and downwardAPI volume types didn't create user-visible files after a kubelet restart. This fix ensures data persistence and accessibility after restarts. (#122807, @carlory)
• Fixed bug where health check could pass while APIServices are missing from aggregated discovery. (#122883, @Jefftree)
• Fixed bug where providing a FieldPath to a CRD Validation Rule would erroneously affect the reported field path of other unrelated CRD Validation Rules on the same schema. (#123475, @alexzielenski)
• Fixed enabling consistent list from watch cache that used to work for resourceVersion=0 (#123676, @serathius)
• Fixed node lifecycle controller panic when conditionType ready is been patch nil by mistake. (#122874, @fusida)
• Fixed panic of Evented PLEG during kubelet start-up. (#122475, @pacoxu)
• Fixed resource deletion failure caused by quota calculation error when InPlacePodVerticalScaling is turned on. (#122701, @carlory)
• For statically provisioned PVs, if their volume source is of CSI type or they have a migrated annotation, when they are deleted, the PersistentVolume controller won't change their phase to the Failed state. With this patch, the external provisioner can remove the finalizer in the next reconcile loop. Unfortunately, if a previously existing PV has the Failed state, this patch won't take effect. Users are required to remove the finalizer manually. (#122030, @carlory)
• Improved the efficiency of NodeAdded QueueingHint by registering UpdateNodeTaint event for plugins that have NodeAdded event but don't have UpdateNodeTaint event. This ensures better requeuing efficiency and prevents Pods from being stuck in the unschedulable pod pool. (#122292, @sanposhiho)
• JWTs used in service account and OIDC authentication are now strictly parsed to confirm that they use compact serialization. Other encodings were not previously accepted, but would result in different unspecific errors. (#123540, @enj)
• Kube-apiserver: Fixed a 1.27+ regression in watch stability by serving watch requests without a resourceVersion from the watch cache by default, as in <1.27 (disabling the change in PR 115096 by default). This mitigates the impact of an etcd watch bug (etcd-io/etcd#17555). If the 1.27 change in PR 115096 to serve these requests from underlying storage is still desired despite the impact on watch stability, it can be re-enabled with a WatchFromStorageWithoutResourceVersion feature gate. (#123935, @serathius)
• Kubeadm: avoided uploading a defaulted flag value "--authorization-mode=Node,RBAC" for the kube-apiserver in the ClusterConfiguration stored in the "kube-system/kubeadm-config" ConfigMap. "Node,RBAC" are already the kubeadm defaults for this flag, so this action is redundant. (#123555, @neolit123)
• Kubeadm: fixed a bug during kubeadm upgrade, where it is not possible to mount a new device and create a symbolic link for /etc/kubernetes (or a sub-directory) so that kubeadm stores its information on the mounted device. (#123406, @SataQiu)
• Kubeadm: the kubelet-finalize phase of kubeadm init no longer requires the kubelet kubeconfig to have a specific authinfo. (#123171, @vrutkovs)
• OpenAPI V2 will no longer publish aggregated API server OpenAPI for group versions that do not match the APIService specified group version. (#123570, @Jefftree)
• Patched a leak of a discovery document that would occur when an Aggregated APIService changed its Spec.Service field and did not change it back. (#123517, @Jefftree)
• Prevented watch cache starvation by moving its watch to separate RPC. Added a SeparateCacheWatchRPC feature flag to disable this behavior. (#123532, @serathius)
• Reverted the QueueingHint implementation for NodeUnschedulable due to potential scenarios where events that make Pods schedulable could be missed. (#122288, @sanposhiho)
• The PersistentVolume controller no longer automatically assigns a default StorageClass to Persistent Volume Claims (PVCs) with an empty storageClassName. (#122704, @carlory)
• The initialization of nodes using external cloud providers now waits for the providerID value to be available before untainting it. This ensures that nodes are not declared Ready without necessary information such as the providerID and zone labels, which are required for integrations like load balancers to function correctly. Cloud providers that do not implement the GetInstanceProviderID method will not require the providerID to be set and will not fail to initialize the node for backward compatibility. (#123713, @aojea)
• Updated google.golang.org/protobuf to v1.33.0 to resolve CVE-2024-24786. (#123758, @liggitt)
• Updated the sample-apiserver manifest example to include correct RBAC configurations. (#123479, @Jefftree)
• When initializing nodes using external cloud-providers, the process now waits for the providerID value to be available before declaring the node ready. This ensures that nodes are not marked as Ready prematurely due to communication errors with the cloud-provider. The providerID and zone labels are necessary for integrations such as load balancers to function correctly. Users can choose to opt out of this behavior by setting the feature flag OptionalProviderID in the cloud-controller-manager. (#123331, @aojea)
• When using kubectl logs <pod-name> and the pod is not found, the error message now includes the namespace. Previously, the message would be "Error from server (NotFound): pods "my-pod-name" not found". Now, it reflects the namespace in the message as follows: "Error from server (NotFound): pods "my-pod-name" not found in namespace "default"". (#120111, @newtondev)
• When using a claim with immediate allocation and a pod referencing that claim couldn't get scheduled, the scheduler incorrectly may have tried to deallocate that claim. (#122415, @pohly)
• [kubeadam][structured authz] avoided setting default --authorization-mode when --authorization-config is provided (#123654, @LiorLieberman)
• ValidateVolumeAttributesClassUpdate also validates new VolumeAttributesClass object. (#122449, @carlory)

• Accepted zero as a default value for kubectl create token duration. (#123565, @ah8ad3)
• Cleanup: removed getStorageAccountName warning messages. (#121983, @andyzhangx)
• Client-go: Optimized leaders renewing leases by updating leader lock optimistically without getting the record from the API server first. Also, a new metric leader_election_slowpath_total was added to allow users to monitor how many leader elections are updated non-optimistically. (#122069, @linxiulei)
• Locked the GA feature-gate ConsistentHTTPGetHandlers to default. (#122578, @carlory)
• Migrated client-go/metadata to contextual logging. (#122225, @ricardoapl)
• Removed the GA feature gate RemoveSelfLink. (#122468, @carlory)
• Removed the generally available feature gate ExpandedDNSConfig. (#122086, @bzsuni)
• Removed the generally available feature gate KubeletPodResourcesGetAllocatable. (#122138, @ii2day)
• Removed the generally available feature gate KubeletPodResources. (#122139, @bzsuni)
• Removed the generally available feature gate MinimizeIPTablesRestore. (#122136, @ty-dc)
• The GA feature-gate APISelfSubjectReview has been removed, and the feature is unconditionally enabled. (#122032, @carlory)
• Updated etcd to version 3.5.12. (#123150, @bzsuni)
• Updated cri-tools to v1.29.0. (#122271, @saschagrunert)
• Upgraded metrics server to v0.7.0. (#123504, @pacoxu)
• kubeadm completion error message now displayed supported shell types when an invalid shell was specified. (#122477, @SataQiu)
• kubeadm: ensured that a variety of API server requests were retried during "init", "join", "upgrade", "reset" workflows. Prior to this change, some API server requests, such as creating or updating ConfigMaps, were "one-shot" - i.e., they could fail if the API server dropped connectivity for a very short period of time. (#123271, @neolit123)
• kubeadm: improved the overall logic, error handling, and output messages when waiting for the kubelet and API server /healthz endpoints to return OK. The kubelet and API server checks no longer ran in parallel, but one after another (in serial). (#121958, @neolit123)
• Added an optimization to reduce stack memory usage for watch requests. It can be disabled with the feature gate: APIServingWithRoutine=false (#120902, @linxiulei)
• Added warning for PV on reclaim policy when it is Recycle. (#122339, @carlory)
• Deprecated the azureFile in-tree storage plugin. (#122576, @carlory)
• Etcd image v3.5.12 has been built. (#123069, @bzsuni)
• Fixed a bug in scheduler requeueing where registered wildcard cluster event sources didn't work. (#123117, @kerthcet)
• Kubeadm: the bridge-nf-call-iptables=1 and bridge-nf-call-ip6tables=1 preflight checks are removed since not all the network implementations require this setting, network plugins are responsible for setting this correctly depending on whether or not they connect containers to Linux bridges or use some other mechanism. (#123464, @SataQiu)
• Kubeadm: used ttlSecondsAfterFinished to automatically clean up the upgrade-health-check Job that runs during upgrade preflighting. (#122079, @carlory)
• Migrated the kube-proxy to use contextual logging. (#122197, @fatsheep9146)
• Promoted feature-gate LegacyServiceAccountTokenCleanUp to GA and locked it to default. (#122635, @carlory)
• Removed GA featuregate about ExperimentalHostUserNamespaceDefaultingGate in 1.30. (#122088, @bzsuni)
• Removed the GA feature gate for IPTablesOwnershipCleanup in version 1.30. (#122137, @bzsuni)
• Removed the generally available feature gate ProxyTerminatingEndpoints. (#122134, @ty-dc)
• The --cidr-allocator-type option set to CloudAllocator for kube-controller-manager will be deprecated and removed in a future release. Users are advised to transition to and explore the available options provided by their external cloud provider. (#123011, @dims)
• The feature gate LegacyServiceAccountTokenTracking (GA since 1.28) is now removed because the feature is unconditionally enabled. (#122409, @Rei1010)
• The in-tree cloud provider for Azure has now been removed. Please use the external cloud provider and CSI driver from https://github.com/kubernetes/cloud-provider-azure instead. (#122857, @nilo19)
• The in-tree cloud provider for vSphere has been deprecated and removed. Users are advised to utilize the external cloud provider and CSI driver available at https://github.com/kubernetes/cloud-provider-vsphere. (#122937, @dims)
• Updated kube-dns to v1.22.27. (#121736, @ty-dc)
• Updated cni-plugins to version v1.4.0. (#122178, @saschagrunert)
• Updated kubedns and nodelocaldns to version v1.23.0. (#123310, @bzsuni)
• kube-proxy nftables mode is now compatible with kernel 5.4. (#122296, @tnqn)
• Renamed Label cluster to storage_cluster_id for apiserver_storage_size_bytes metric (#124283, dims)
• Bumped the stability level of apiserver_storage_size_bytes to STABLE (#123342, @logicalhan)

• Fixed an issue where kubectl apply could panic when imported as a library. (#122346, @Jefftree)

• github.com/fxamacker/cbor/v2: v2.6.0
• github.com/pkg/diff: 20ebb0f
• github.com/x448/float16: v0.8.4
• golang.org/x/telemetry: b75ee88
• k8s.io/gengo/v2: 51d4e06
• sigs.k8s.io/knftables: v0.0.14

• github.com/docker/docker: v20.10.24+incompatible → v20.10.27+incompatible
• github.com/go-logr/logr: v1.3.0 → v1.4.1
• github.com/go-logr/zapr: v1.2.3 → v1.3.0
• github.com/golang/protobuf: v1.5.3 → v1.5.4
• github.com/google/cadvisor: v0.48.1 → v0.49.0
• github.com/google/cel-go: v0.17.7 → v0.17.8
• github.com/onsi/ginkgo/v2: v2.13.0 → v2.15.0
• github.com/onsi/gomega: v1.29.0 → v1.31.0
• github.com/opencontainers/runc: v1.1.10 → v1.1.12
• go.uber.org/atomic: v1.10.0 → v1.7.0
• go.uber.org/goleak: v1.2.1 → v1.3.0
• go.uber.org/zap: v1.19.0 → v1.26.0
• golang.org/x/crypto: v0.14.0 → v0.21.0
• golang.org/x/mod: v0.12.0 → v0.15.0
• golang.org/x/net: v0.17.0 → v0.23.0
• golang.org/x/sync: v0.3.0 → v0.6.0
• golang.org/x/sys: v0.13.0 → v0.18.0
• golang.org/x/term: v0.13.0 → v0.18.0
• golang.org/x/text: v0.13.0 → v0.14.0
• golang.org/x/tools: v0.12.0 → v0.18.0
• google.golang.org/protobuf: v1.31.0 → v1.33.0
• k8s.io/klog/v2: v2.110.1 → v2.120.1
• k8s.io/kube-openapi: 2dd684a → 70dd376
• sigs.k8s.io/apiserver-network-proxy/konnectivity-client: v0.28.0 → v0.29.0

• github.com/Azure/azure-sdk-for-go: v68.0.0+incompatible
• github.com/Azure/go-autorest/autorest/adal: v0.9.23
• github.com/Azure/go-autorest/autorest/date: v0.3.0
• github.com/Azure/go-autorest/autorest/mocks: v0.4.2
• github.com/Azure/go-autorest/autorest/to: v0.4.0
• github.com/Azure/go-autorest/autorest/validation: v0.3.1
• github.com/Azure/go-autorest/autorest: v0.11.29
• github.com/Azure/go-autorest/logger: v0.2.1
• github.com/Azure/go-autorest/tracing: v0.6.0
• github.com/Azure/go-autorest: v14.2.0+incompatible
• github.com/a8m/tree: 10a5fd5
• github.com/benbjohnson/clock: v1.1.0
• github.com/danwinship/knftables: v0.0.13
• github.com/dnaeon/go-vcr: v1.2.0
• github.com/dougm/pretty: 2ee9d74
• github.com/gofrs/uuid: v4.4.0+incompatible
• github.com/rasky/go-xdr: 4930550
• github.com/rubiojr/go-vhd: 02e2102
• github.com/vmware/govmomi: v0.30.6
• github.com/vmware/vmw-guestinfo: 25eff15
• k8s.io/gengo: 9cce18d

All container images are available as manifest lists and support the described architectures. It is also possible to pull a specific architecture directly by adding the "-$ARCH" suffix to the container image name.

• Kubernetes is now built with go 1.22.2 (#124196, @cpanato) [SIG Release and Testing]

• Golang.org/x/net is bumped to v0.23.0 to address CVE-2023-45288 (#124174, @dims) [SIG API Machinery, Architecture, Auth, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Network, Node and Storage]

Nothing has changed.

• golang.org/x/crypto: v0.19.0 → v0.21.0
• golang.org/x/net: v0.21.0 → v0.23.0
• golang.org/x/sys: v0.17.0 → v0.18.0
• golang.org/x/term: v0.17.0 → v0.18.0

Nothing has changed.

All container images are available as manifest lists and support the described architectures. It is also possible to pull a specific architecture directly by adding the "-$ARCH" suffix to the container image name.

• Fix pod restart after node reboot when NewVolumeManagerReconstruction feature gate is enabled and SELinuxMountReadWriteOncePod disabled (#124048, @bertinatto) [SIG Node]
• Kubeadm: fix panic in the command "kubeadm certs check-expiration" when "/etc/kubernetes/pki" exists but cannot be read. (#124124, @carlory) [SIG Cluster Lifecycle]

Nothing has changed.

Nothing has changed.

Nothing has changed.

All container images are available as manifest lists and support the described architectures. It is also possible to pull a specific architecture directly by adding the "-$ARCH" suffix to the container image name.

• Revert "support sharing waitingPods across different scheduler profiles" (#124001, @kerthcet) [SIG Scheduling]

• Currently, NodeAdded QueueingHint could not always be called because of the internal feature called preCheck. It's definitely not something expected for plugin developers, and we're trying to eventually remove preCheck completely to fix this. Until then we'll register UpdateNodeTaint event for plugins that have NodeAdded event, but don't have UpdateNodeTaint event. It'd result in a bad impact on the requeuing efficiency though, a lot better than some Pods being stuck in the unschedulable pod pool. (#122292, @sanposhiho) [SIG Node, Scheduling, Storage and Testing]
• Fix enabling consistent list from watch cache also works for resourceVersion=0 (#123676, @serathius) [SIG API Machinery]
• Kube-apiserver: fixes a 1.27+ regression in watch stability by serving watch requests without a resourceVersion from the watch cache by default, as in <1.27 (disabling the change in #115096 by default). This mitigates the impact of an etcd watch bug (etcd-io/etcd#17555). If the 1.27 change in #115096 to serve these requests from underlying storage is still desired despite the impact on watch stability, it can be re-enabled with a WatchFromStorageWithoutResourceVersion feature gate. (#123935, @serathius) [SIG API Machinery and Etcd]

Nothing has changed.

Nothing has changed.

Nothing has changed.

All container images are available as manifest lists and support the described architectures. It is also possible to pull a specific architecture directly by adding the "-$ARCH" suffix to the container image name.

• A new (alpha) field, trafficDistribution, has been added to the Service spec. This field provides a way to express preferences for how traffic is distributed to the endpoints for a Service. It can be enabled through the ServiceTrafficDistribution feature gate. (#123487, @gauravkghildiyal) [SIG API Machinery, Apps and Network]

• Add alpha-level support for the SuccessPolicy in Jobs (#123412, @tenzen-y) [SIG API Machinery, Apps and Testing]

• Added (alpha) support for the managedBy field on Jobs. Jobs with a custom value of this field - any value other than kubernetes.io/job-controller - are skipped by the job controller, and their reconciliation is delegated to an external controller, indicated by the value of the field. Jobs that don't have this field at all, or where the field value is the reserved string kubernetes.io/job-controller, are reconciled by the built-in job controller. (#123273, @mimowo) [SIG API Machinery, Apps and Testing]

• Added a alpha feature, behind the RelaxedEnvironmentVariableValidation feature gate. When that gate is enabled, Kubernetes allows almost all printable ASCII characters to be used in the names of environment variables for containers in Pods. (#123385, @HirazawaUi) [SIG Apps, Node and Testing]

• Added alpha support for field selectors on custom resources. Provided that the CustomResourceFieldSelectors feature gate is enabled, the CustomResourceDefinition API now lets you specify selectableFields. Listing a field there allows filtering custom resources for that CustomResourceDefinition in list or watch requests. (#122717, @jpbetz) [SIG API Machinery]

• Added support for configuring multiple JWT authenticators in Structured Authentication Configuration. The maximum allowed JWT authenticators in the authentication configuration is 64. (#123431, @aramase) [SIG Auth and Testing]

• Aggregated discovery supports both v2beta1 and v2 types and feature is promoted to GA (#122882, @Jefftree) [SIG API Machinery and Testing]

• Allowing container runtimes to fix an image garbage collection bug by adding an image_id field to the CRI Container message. (#123508, @saschagrunert) [SIG Node]

• AppArmor profiles can now be configured through fields on the PodSecurityContext and container SecurityContext.

  • The beta AppArmor annotations are deprecated.
  • AppArmor status is no longer included in the node ready condition (#123435, @tallclair) [SIG API Machinery, Apps, Auth, Node and Testing]

• Conflicting issuers between JWT authenticators and service account config are now detected and fail on API server startup. Previously such a config would run but would be inconsistently effective depending on the credential. (#123561, @enj) [SIG API Machinery and Auth]

• Dynamic Resource Allocation: DRA drivers may now use "structured parameters" to let the scheduler handle claim allocation. (#123516, @pohly) [SIG API Machinery, Apps, Auth, CLI, Cluster Lifecycle, Instrumentation, Node, Release, Scheduling, Storage and Testing]

• Graduated pod scheduling gates to general availability. The PodSchedulingReadiness feature gate no longer has any effect, and the .spec.schedulingGates field is always available within the Pod and PodTemplate APIs. (#123575, @Huang-Wei) [SIG API Machinery, Apps, Node, Scheduling and Testing]

• Graduated support for minDomains in pod topology spread constraints, to general availability. The MinDomainsInPodTopologySpread feature gate no longer has any effect, and the field is always available within the Pod and PodTemplate APIs. (#123481, @sanposhiho) [SIG API Machinery, Apps, Scheduling and Testing]

• JWT authenticator config set via the --authentication-config flag is now dynamically reloaded as the file changes on disk. (#123525, @enj) [SIG API Machinery, Auth and Testing]

• Kube-apiserver: the AuthenticationConfiguration type accepted in --authentication-config files has been promoted to apiserver.config.k8s.io/v1beta1. (#123696, @aramase) [SIG API Machinery, Auth and Testing]

• Kube-apiserver: the AuthorizationConfiguration type accepted in --authorization-config files has been promoted to apiserver.config.k8s.io/v1beta1. (#123640, @liggitt) [SIG Auth and Testing]

• Kubelet should fail if NodeSwap is used with LimitedSwap and cgroupv1 node. (#123738, @kannon92) [SIG API Machinery, Node and Testing]

• Kubelet: a custom root directory for pod logs (instead of default /var/log/pods) can be specified using the podLogsDir key in kubelet configuration. (#112957, @mxpv) [SIG API Machinery, Node, Scalability and Testing]

• Kubelet: the .memorySwap.swapBehavior field in kubelet configuration accepts a new value NoSwap and makes this the default if unspecified; the previously accepted UnlimitedSwap value has been dropped. (#122745, @kannon92) [SIG API Machinery, Node and Testing]

• OIDC authentication will now fail if the username asserted based on a CEL expression config is the empty string. Previously the request would be authenticated with the username set to the empty string. (#123568, @enj) [SIG API Machinery, Auth and Testing]

• PodSpec API: remove note that hostAliases are not supported on hostNetwork Pods. The feature has been supported since v1.8. (#122422, @neolit123) [SIG API Machinery and Apps]

• Promote AdmissionWebhookMatchConditions to GA. The feature is now stable and the feature gate is now locked to default. (#123560, @ivelichkovich) [SIG API Machinery and Testing]

• Structured Authentication Configuration now supports DiscoveryURL. discoveryURL if specified, overrides the URL used to fetch discovery information. This is for scenarios where the well-known and jwks endpoints are hosted at a different location than the issuer (such as locally in the cluster). (#123527, @aramase) [SIG API Machinery, Auth and Testing]

• Support Recursive Read-only (RRO) mounts (KEP-3857) (#123180, @AkihiroSuda) [SIG API Machinery, Apps, Node and Testing]

• The StructuredAuthenticationConfiguration feature is now beta and enabled by default. (#123719, @enj) [SIG API Machinery and Auth]

• The StorageVersionMigration API, which was previously available as a Custom Resource Definition (CRD), is now a built-in API in Kubernetes. (#123344, @nilekhc) [SIG API Machinery, Apps, Auth, CLI and Testing]

• The kubernetes repo now uses Go workspaces. This should not impact end users at all, but does have impact for developers of downstream projects. Switching to workspaces caused some breaking changes in the flags to the various k8s.io/code-generator tools. Downstream consumers should look at staging/src/k8s.io/code-generator/kube_codegen.sh to see the changes. (#123529, @thockin) [SIG API Machinery, Apps, Architecture, Auth, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Network, Node, Release, Storage and Testing]

• ValidatingAdmissionPolicy is promoted to GA and will be enabled by default. (#123405, @cici37) [SIG API Machinery, Apps, Auth and Testing]

• When configuring a JWT authenticator:

  If username.expression uses 'claims.email', then 'claims.email_verified' must be used in username.expression or extra[].valueExpression or claimValidationRules[].expression. An example claim validation rule expression that matches the validation automatically applied when username.claim is set to 'email' is 'claims.?email_verified.orValue(true)'. (#123737, @enj) [SIG API Machinery and Auth]

• Added access_mode label to volume_manager_selinux_* metrics. (#123667, @jsafrane) [SIG Node, Storage and Testing]

• Added client-go support for upgrading subresource fields from client-side to server-side management (#123484, @erikgb) [SIG API Machinery]

• Added apiserver_watch_cache_read_wait metric to measure watch cache impact on request latency. (#123190, @padlar) [SIG API Machinery and Instrumentation]

• Adds new flag, namely custom, in kubectl debug to let users customize pre-defined profiles. (#120346, @ardaguclu) [SIG CLI]

• Bump cAdvisor to v0.49.0 (#123599, @bobbypage) [SIG Node]

• Embed Node information into Pod-bound service account tokens as additional metadata

  • Set the 'JTI' field in issued service account tokens, and embed this information as authentication.kubernetes.io/credential-id in user's ExtraInfo (#123135, @munnerz) [SIG API Machinery, Auth and Testing]

• Feature gates for RemoteCommand (kubectl exec, cp, and attach) over WebSockets are now enabled by default (Beta).

  • Server-side feature gate: TranslateStreamCloseWebsocketRequests
  • Client-side (kubectl) feature gate: KUBECTL_REMOTE_COMMAND_WEBSOCKETS
  • To turn off RemoteCommand over WebSockets for kubectl, the environment variable feature gate must be explicitly set - KUBECTL_REMOTE_COMMAND_WEBSOCKETS=false (#123281, @seans3) [SIG API Machinery, CLI and Testing]

• Graduated HorizontalPodAutoscaler support for per-container metrics to stable. (#123482, @sanposhiho) [SIG API Machinery, Apps and Autoscaling]

• Graduated forensic container checkpointing KEP #2008 from Alpha to Beta. (#123215, @adrianreber) [SIG Node and Testing]

• In the Pod API, setting the alpha procMount field to Unmasked in a container now requires setting spec.hostUsers=false as well. (#123520, @haircommander) [SIG Apps, Auth and Testing]

• InitContainer's image location will be considered in scheduling when prioritizing nodes. (#123366, @kerthcet) [SIG Scheduling]

• It is possible to configure the IDs that the Kubelet uses to create user namespaces.

  User namespaces support is a Beta feature now. (#123593, @giuseppe) [SIG Node]

• Kube-apiserver now reports latency metric for JWT authenticator authenticate token decisions in the apiserver_authentication_jwt_authenticator_latency_seconds metric, labeled by jwtIssuer hash and result. (#123225, @aramase) [SIG API Machinery and Auth]

• Kube-apiserver now reports the following metrics for authorization webhook match conditions:

  • apiserver_authorization_match_condition_evaluation_errors_total counter metric labeled by authorizer type and name
  • apiserver_authorization_match_condition_exclusions_total counter metric labeled by authorizer type and name
  • apiserver_authorization_match_condition_evaluation_seconds histogram metric labeled by authorizer type and name (#123611, @ritazh) [SIG API Machinery, Auth and Testing]

• Kube-apiserver: Authorization webhooks now report the following metrics:

  • apiserver_authorization_webhook_evaluations_total
  • apiserver_authorization_webhook_duration_seconds
  • apiserver_authorization_webhook_evaluations_fail_open_total (#123639, @liggitt) [SIG API Machinery, Auth and Testing]

• Kube-apiserver: JWT authenticator now report the following metrics:

  • apiserver_authentication_config_controller_automatic_reloads_total
  • apiserver_authentication_config_controller_automatic_reload_last_timestamp_seconds (#123793, @aramase) [SIG API Machinery, Auth and Testing]

• Kube-apiserver: the StructuredAuthorizationConfiguration feature gate is promoted to beta and allows using the --authorization-configuration flag (#123641, @liggitt) [SIG API Machinery and Auth]

• Kube-controller-manager: increase the global level for broadcaster's logging to 3 so that users can ignore event messages by lowering the logging level. It reduces information noise. (#122293, @mengjiao-liu) [SIG API Machinery, Apps, Autoscaling, Network, Node, Scheduling, Storage and Testing]

• Kubeadm: add the WaitForAllControlPlaneComponents feature gate. It can be used to tell kubeadm to wait for all control plane components to be ready when running "kubeadm init" or "kubeadm join --control-plane". Currently kubeadm only waits for the kube-apiserver. The "kubeadm join" workflow now includes a new experimental phase called "wait-control-plane". This phase will be marked as non-experimental when WaitForAllControlPlaneComponents becomes GA. Accordingly a "kubeadm init" phase "wait-control-plane" will also be available once WaitForAllControlPlaneComponents becomes GA. These phases can be skipped if the user prefers to not wait for the control plane components. (#123341, @neolit123) [SIG Cluster Lifecycle]

• Kubeadm: print all the kubelets and nodes that need to be upgraded on "upgrade plan". (#123578, @carlory) [SIG Cluster Lifecycle]

• Kubectl port-forward over websockets (tunneling SPDY) can be enabled using an Alpha feature flag environment variable: KUBECTL_PORT_FORWARD_WEBSOCKETS=true. The API Server being communicated to must also have an Alpha feature flag enabled: PortForwardWebsockets. (#123413, @seans3) [SIG API Machinery, CLI, Node and Testing]

• Kubernetes is now built with go 1.22.1 (#123750, @cpanato) [SIG Release and Testing]

• Node podresources API now includes init containers with containerRestartPolicy of Always when SidecarContainers feature is enabled. (#120718, @gjkim42) [SIG Node and Testing]

• Promote ImageMaximumGCAge feature to beta (#123424, @haircommander) [SIG Node and Testing]

• Promote PodHostIPs condition to GA and lock to default. (#122870, @wzshiming) [SIG Apps, Network, Node and Testing]

• Target drop-in kubelet configuration dir feature to Beta (#122907, @sohankunkerkar) [SIG Node and Testing]

• The Kubelet rejects creating the pod if hostUserns=false and the CRI runtime does not support user namespaces. (#123216, @giuseppe) [SIG Node]

• The watch cache waits until it is at least as fresh as given requestedWatchRV if sendInitialEvents was requested. (#122830, @p0lyn0mial) [SIG API Machinery, Network and Testing]

• ValidatingAdmissionPolicy now exclude TokenReview, SelfSubjectReview, LocalSubjectAccessReview, and SubjectAccessReview from all versions of authentication.k8s.io and authorization.k8s.io group. (#123543, @jiahuif) [SIG API Machinery and Testing]

• kubectl get job now displays the status for the listed jobs. (#123226, @ivanvc) [SIG Apps and CLI]

• Adds the namespace when using 'kubectl logs ' and the pod is not found. Previously the message returned would be 'Error from server (NotFound): pods "my-pod-name" not found'. This has been updated to reflect the namespace in the message as follows: 'Error from server (NotFound): pods "my-pod-name" not found in namespace "default"' (#120111, @newtondev) [SIG CLI]
• DRA: ResourceClaim and PodSchedulingContext status updates no longer allow changing object meta data. (#123730, @pohly) [SIG Node]
• Fix CEL estimated cost to for expressions that perform operations on the result of map() operations, (e.g. .map(...).exists(...) ) to have the correct estimated instead of an unbounded cost. (#123562, @jpbetz) [SIG API Machinery, Auth and Cloud Provider]
• Fix node lifecycle controller panic when conditionType ready is been patch nil by mistake (#122874, @fusida) [SIG Apps, Network and Node]
• Fix non-recursive list returning "resource version too high" error when consistent list from cache is enabled (#123674, @serathius) [SIG API Machinery]
• Fixed a bug that an init container with containerRestartPolicy with Always cannot update its state from terminated to non-terminated for the pod with restartPolicy with Never or OnFailure. (#123323, @gjkim42) [SIG Apps and Node]
• Fixed incorrect syncCronJob error logging. (#122493, @mengjiao-liu) [SIG Apps]
• Fixed the disruption controller's PDB status synchronization to maintain all PDB conditions during an update. (#122056, @dhenkel92) [SIG Apps]
• Fixes bug where providing a fieldpath to a CRD Validation Rule would erroneously affect the reported field path of other unrelated CRD Validation Rules on the same schema (#123475, @alexzielenski) [SIG API Machinery]
• JWTs used in service account and OIDC authentication are now strictly parsed to confirm that they use compact serialization. Other encodings were not previously accepted, but would result in different unspecific errors. (#123540, @enj) [SIG API Machinery and Auth]
• Kubeadm: in the new output API "output.kubeadm.k8s.io/v1alpha3" modify the UpgradePlan structure that is used when calling "kubeadm upgrade plan ... -o yaml|json", to include a list of multiple available upgrades. (#123461, @carlory) [SIG Cluster Lifecycle]
• Kubeadm: avoid uploading a defaulted flag value "--authorization-mode=Node,RBAC" for the kube-apiserver in the ClusterConfiguration stored in the "kube-system/kubeadm-config" ConfigMap. "Node,RBAC" are already the kubeadm defaults for this flag, so this action is redundant. (#123555, @neolit123) [SIG Cluster Lifecycle]
• OpenAPI V2 will no longer publish aggregated apiserver OpenAPI for group-versions not matching the APIService specified group version (#123570, @Jefftree) [SIG API Machinery]
• Prevent watch cache starvation by moving its watch to separate RPC and add a SeparateCacheWatchRPC feature flag to disable this behavior (#123532, @serathius) [SIG API Machinery]
• The initialization of nodes using external cloud-providers now waits for the providerID value to be available before declaring the node ready. This is required because previously, if there were errors of communication with the cloud-provider on the cloud-controller-manager, nodes may have been declared Ready without having this field or the zone labels, and the information was never reconciled. The providerID and the zone labels are required for integrations like loadbalancers to work correctly. Users still can opt-out to this new behavior by setting the feature flag OptionalProviderID in the cloud-controller-manager. (#123331, @aojea) [SIG API Machinery, Cloud Provider and Testing]
• The initialization of nodes using external cloud-providers now waits for the providerID value to be available before untainting it. This is required because , if there are communication errors with the cloud-provider on the cloud-controller-manager, nodes may have been declared Ready without having this field or the zone labels, and this information was never reconciled. The providerID and the zone labels are required for integrations like loadbalancers to work correctly. Cloud providers that does not implement the GetInstanceProviderID method will not require the providerID to be set and will not fail to initialize the node for backward compatibility issues. (#123713, @aojea) [SIG Cloud Provider]
• Updates google.golang.org/protobuf to v1.33.0 to resolve CVE-2024-24786 (#123758, @liggitt) [SIG API Machinery, Architecture, Auth, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Network, Node and Storage]
• [kubeadam][structured authz] avoid setting default --authorization-mode when --authorization-config is provided (#123654, @LiorLieberman) [SIG Cluster Lifecycle]

• Accept zero as a default value for kubectl create token duration (#123565, @ah8ad3) [SIG CLI]
• Update kubedns and nodelocaldns to v1.23.0 (#123310, @bzsuni) [SIG Cloud Provider]

• github.com/pkg/diff: 20ebb0f
• golang.org/x/telemetry: b75ee88
• k8s.io/gengo/v2: 51d4e06

• github.com/docker/docker: v20.10.24+incompatible → v20.10.27+incompatible
• github.com/golang/protobuf: v1.5.3 → v1.5.4
• github.com/google/cadvisor: v0.48.1 → v0.49.0
• github.com/google/cel-go: v0.17.7 → v0.17.8
• golang.org/x/mod: v0.14.0 → v0.15.0
• golang.org/x/net: v0.19.0 → v0.21.0
• golang.org/x/sync: v0.5.0 → v0.6.0
• golang.org/x/tools: v0.16.1 → v0.18.0
• google.golang.org/protobuf: v1.31.0 → v1.33.0
• k8s.io/kube-openapi: 778a556 → 70dd376

• k8s.io/gengo: 9cce18d

All container images are available as manifest lists and support the described architectures. It is also possible to pull a specific architecture directly by adding the "-$ARCH" suffix to the container image name.

• Added a CBOR implementation of runtime.Serializer. Until CBOR graduates to Alpha, API servers will refuse to start if configured with CBOR support. (#122881, @benluddy) [SIG API Machinery]

• Added audienceMatchPolicy field to AuthenticationConfiguration and support for configuring multiple audiences.

  • The "audienceMatchPolicy" can be empty (or unset) when a single audience is specified in the "audiences" field.
  • The "audienceMatchPolicy" must be set to "MatchAny" when multiple audiences are specified in the "audiences" field. (#123165, @aramase) [SIG API Machinery, Auth and Testing]

• Contextual logging is now beta and enabled by default. (#122589, @pohly) [SIG Instrumentation]

• Cri-api: KEP-3857: Recursive Read-only (RRO) mounts (#123272, @AkihiroSuda) [SIG Node]

• Enabled a mechanism for concurrent log rotatation via kubelet using a configuration entity of containerLogMaxWorkers which controls the maximum number of concurrent rotation that can be performed and an interval configuration of containerLogMonitorInterval that can aid is configuring the monitoring duration to best suite your cluster's log generation standards. (#114301, @harshanarayana) [SIG API Machinery, Node and Testing]

• Text logging in Kubernetes components now uses textlogger. The same split streams of info and error log entries with buffering of info entries is now also supported for text output (off by default, alpha feature). Previously, this was only supported for JSON. Performance is better also without split streams. (#114672, @pohly) [SIG API Machinery, Architecture, Auth, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Network, Node, Storage and Testing]

• This change adds the following CLI option for kube-controller-manager:

  • disable-force-detach (defaults to false): Prevent force detaching volumes based on maximum unmount time and node status. If enabled, the non-graceful node shutdown feature must be used to recover from node failure (see https://kubernetes.io/blog/2023/08/16/kubernetes-1-28-non-graceful-node-shutdown-ga/). If enabled and a pod must be forcibly terminated at the risk of corruption, then the appropriate VolumeAttachment object (see here: https://kubernetes.io/docs/reference/kubernetes-api/config-and-storage-resources/volume-attachment-v1/) must be deleted. (#120344, @rohitssingh) [SIG API Machinery, Apps, Storage and Testing]

• A new kubelet metric image_pull_duration_seconds is added. The metric tracks the duration (in seconds) it takes for an image to be pulled, including the time spent in the waiting queue of image puller. The metric is broken down by bucketed image size. (#121719, @ruiwen-zhao) [SIG Instrumentation and Node]
• A new metric lifecycle_handler_sleep_terminated_total is added to record how many times LifecycleHandler sleep got unexpectedly terminated. (#122456, @AxeZhan) [SIG Node and Testing]
• Add "reason" field to image_garbage_collected_total metric, so admins can differentiate images that were collected for reason "age" vs "space" (#123345, @haircommander) [SIG Node]
• Add feature gate MutatingAdmissionPolicy for enabling mutation policy in admission chain. (#123425, @cici37) [SIG API Machinery]
• Add kubelet metrics to track the memory manager allocation and pinning (#121778, @Tal-or) [SIG Node and Testing]
• Added support for cloud provider integrations to supply optional, per-Node custom labels that will be applied to Nodes by the node controller. Extra labels will only be applied where the cloud provider integration implements this. (#123223, @mmerkes) [SIG Cloud Provider]
• Kube-apiserver now reloads the --authorization-config file when it changes. Reloads increment the apiserver_authorization_config_controller_automatic_reload_last_timestamp_seconds timestamp metric, with status="success" for successful reloads and status="failed" for failed reloads. Failed reloads keep using the previously loaded authorization configuration. (#121946, @liggitt) [SIG API Machinery, Auth and Testing]
• Kube-apiserver now reports metrics for authorization decisions in the apiserver_authorization_decisions_total metric, labeled by authorizer type, name, and decision. (#123333, @liggitt) [SIG API Machinery, Auth and Testing]
• Kubeadm: add support for machine readable output with "-o yaml" and "-o json" to the command "kubeadm certs check-expiration". This change is added in a new API "kind": "CertificateExpirationInfo", "apiVersion": "output.kubeadm.k8s.io/v1alpha3". The existing non structured formatting is preserved. The output API version v1alpha2 is now deprecated and will be removed in a future release. Please migrate to using v1alpha3. (#123372, @carlory) [SIG Cluster Lifecycle]
• LoadBalancerIPMode feature is now marked as Beta (#123418, @rikatz) [SIG Network and Testing]
• New alpha feature gate SELinuxMount can be used to speed up SELinux relabeling of volumes. (#123157, @jsafrane) [SIG Node and Storage]
• NewVolumeManagerReconstruction feature is now GA. (#123442, @jsafrane) [SIG Node]
• Promoted the CRDValidationRatcheting feature gate to beta, and made it enabled by default. (#121461, @alexzielenski) [SIG API Machinery and Testing]
• Update ImageGCMaxAge behavior in the kubelet to wait the MaxAge duration after the kubelet has restarted before garbage collecting (#123343, @haircommander) [SIG Node and Testing]
• When the RetryGenerateName feature gate is enabled on the kube-apiserver, create requests using generateName are retried automatically by the apiserver when the generated name conflicts with an existing resource name, up to a max limit of 7 retries. This feature is in alpha. (#122887, @jpbetz) [SIG API Machinery]

• Add a new internal metric in the kubelet that allow developers to understand the source of the latency problems on node startups.

  kubelet_first_network_pod_start_sli_duration_seconds (#121720, @aojea) [SIG Instrumentation, Network and Node]

• DRA: fixed potential data race with no known real-world implications. (#123222, @pohly) [SIG Node]
• Fix bug where health check could pass while APIServices are missing from aggregated discovery (#122883, @Jefftree) [SIG API Machinery and Testing]
• Fixed an issue where a JWT authenticator configured via --authentication-config would fail to verify tokens that were not signed using RS256. (#123282, @enj) [SIG API Machinery, Auth and Testing]
• Improves scheduler performance when no scoring plugins are defined. (#123384, @aleksandra-malinowska) [SIG Scheduling]
• Kubeadm: fix a bug during kubeadm upgrade, where it is not possible to mount a new device and create a symbolic link for /etc/kubernetes (or a sub-directory) so that kubeadm stores its information on the mounted device. (#123406, @SataQiu) [SIG Cluster Lifecycle]
• Kubeadm: fix a bug where "kubeadm upgrade plan -o yaml|json" includes unneeded output and was missing component config information. (#123492, @carlory) [SIG Cluster Lifecycle]
• Patches a leak of a discovery document that would occur when an Aggregated APIService changed its Spec.Service field and did not change it back. (#123517, @Jefftree) [SIG API Machinery]
• Restore --verify-only function in code generation wrappers. (#123261, @skitt) [SIG API Machinery]
• Sample-apiserver manifest example will have correct RBAC (#123479, @Jefftree) [SIG API Machinery and Testing]

• An optimization is implemented to reduce stack memory usage for watch requests. It is can be disabled with the feature gate: APIServingWithRoutine=false (#120902, @linxiulei) [SIG API Machinery]
• Kubeadm: make sure that a variety of API server requests are retried during "init", "join", "upgrade", "reset" workflows. Prior to this change some API server requests, such as, creating or updating ConfigMaps were "one-shot" - i.e. they could fail if the API server dropped connectivity for a very short period of time. (#123271, @neolit123) [SIG Cluster Lifecycle]
• Kubeadm: the bridge-nf-call-iptables=1 and bridge-nf-call-ip6tables=1 preflight checks are removed since not all the network implementations require this setting, network plugins are responsible for setting this correctly depending on whether or not they connect containers to Linux bridges or use some other mechanism. (#123464, @SataQiu) [SIG Cluster Lifecycle]
• Upgrade metrics server to v0.7.0 (#123504, @pacoxu) [SIG Cloud Provider and Instrumentation]

Nothing has changed.

• github.com/fxamacker/cbor/v2: v2.5.0 → v2.6.0
• golang.org/x/crypto: v0.16.0 → v0.19.0
• golang.org/x/sys: v0.15.0 → v0.17.0
• golang.org/x/term: v0.15.0 → v0.17.0

Nothing has changed.

All container images are available as manifest lists and support the described architectures. It is also possible to pull a specific architecture directly by adding the "-$ARCH" suffix to the container image name.

• Removed the SecurityContextDeny admission plugin, deprecated since v1.27. The Pod Security Admission plugin, available since v1.25, is recommended instead. See https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#securitycontextdeny for more information. (#122612, @mtardy) [SIG Auth, Security and Testing]

• Updated an audit annotation key used by the …/serviceaccounts/<name>/token resource handler. The annotation used to persist the issued credential identifier is now authentication.kubernetes.io/issued-credential-id. (#123098, @munnerz) [SIG Auth]

• Add apiserver.latency.k8s.io/decode-response-object annotation to the audit log to record the decoding time (#121512, @HirazawaUi) [SIG API Machinery]
• Added apiserver_encryption_config_controller_automatic_reloads_total to measure total number of reload successes and failures of encryption configuration. This metric contains the status label with enum value of success and failure.
  • Deprecated apiserver_encryption_config_controller_automatic_reload_success_total and apiserver_encryption_config_controller_automatic_reload_failure_total metrics. Use apiserver_encryption_config_controller_automatic_reloads_total instead. (#123179, @aramase) [SIG API Machinery, Auth and Testing]
• Allow a zero value for the 'nominalConcurrencyShares' field of the PriorityLevelConfiguration object either using the flowcontrol.apiserver.k8s.io/v1 or flowcontrol.apiserver.k8s.io/v1beta3 API (#123001, @tkashem) [SIG API Machinery]
• Graduated support for passing dual-stack kubelet --node-ip values when using a cloud provider. The feature is now GA and the CloudDualStackNodeIPs feature gate is always enabled. (#123134, @danwinship) [SIG API Machinery, Cloud Provider and Node]
• Kubernetes is now built with go 1.22 (#123217, @cpanato) [SIG Release and Testing]
• The scheduler retries Pods, which are failed by nodevolumelimits due to not found PVCs, only when new PVCs are added. (#121952, @sanposhiho) [SIG Scheduling and Storage]
• Update distroless-iptables to v0.5.0 debian-base to bookworm-v1.0.1 and setcap to bookworm-v1.0.1 (#123170, @cpanato) [SIG API Machinery, Architecture, Cloud Provider, Release, Storage and Testing]
• Users can traverse all the pods that are in the scheduler and waiting in the permit stage through method IterateOverWaitingPods. In other words, all waitingPods in scheduler can be obtained from any profiles. Before this commit, each profile could only obtain waitingPods within that profile. (#122946, @NoicFank) [SIG Scheduling]
• ValidatingAdmissionPolicy now supports type checking policies that make use of variables. (#123083, @jiahuif) [SIG API Machinery]

• Fix Pod stuck in Terminating because of GenerateUnmapVolumeFunc missing globalUnmapPath when kubelet tries to clean up all volumes that failed reconstruction. (#123032, @carlory) [SIG Storage]
• Fix deprecated version for pod_scheduling_duration_seconds that caused the metric to be hidden by default in 1.29. (#123038, @alculquicondor) [SIG Instrumentation and Scheduling]
• Fix error when trying to expand a volume that does not require node expansion (#123055, @gnufied) [SIG Node and Storage]
• Fix the following volume plugins may not create user visible files after kubelet was restarted.
  • configmap
  • secret
  • projected
  • downwardapi (#122807, @carlory) [SIG Storage]
• Fixed cleanup of Pod volume mounts when a file was used as a subpath. (#123052, @jsafrane) [SIG Node]
• Fixes an issue calculating total CPU usage reported for Windows nodes (#122999, @marosset) [SIG Node and Windows]
• Fixing issue where AvailableBytes sometimes does not report correctly on WindowsNodes when PodAndContainerStatsFromCRI feature is enabled. (#122846, @marosset) [SIG Node and Windows]
• Kubeadm: do not upload kubelet patch configuration into kube-system/kubelet-config ConfigMap (#123093, @SataQiu) [SIG Cluster Lifecycle]
• Kubeadm: fix a bug where the --rootfs global flag does not work with "kubeadm upgrade node" for control plane nodes. (#123077, @neolit123) [SIG Cluster Lifecycle]
• Kubeadm: kubelet-finalize phase of "kubeadm init" no longer requires kubelet kubeconfig to have a specific authinfo (#123171, @vrutkovs) [SIG Cluster Lifecycle]
• Show enum values in kubectl explain if they were defined (#123023, @ah8ad3) [SIG CLI]

• Build etcd image v3.5.12 (#123069, @bzsuni) [SIG API Machinery and Etcd]
• Fix registered wildcard clusterEvents doesn't work in scheduler requeueing. (#123117, @kerthcet) [SIG Scheduling]
• Promote feature-gate LegacyServiceAccountTokenCleanUp to GA and lock to default (#122635, @carlory) [SIG API Machinery, Auth and Testing]
• Update etcd to version 3.5.12 (#123150, @bzsuni) [SIG API Machinery, Cloud Provider, Cluster Lifecycle and Testing]

• github.com/fxamacker/cbor/v2: v2.5.0
• github.com/x448/float16: v0.8.4

• github.com/opencontainers/runc: v1.1.11 → v1.1.12
• sigs.k8s.io/apiserver-network-proxy/konnectivity-client: v0.28.0 → v0.29.0

Nothing has changed.

All container images are available as manifest lists and support the described architectures. It is also possible to pull a specific architecture directly by adding the "-$ARCH" suffix to the container image name.

• Kubectl: remove deprecated flag prune-whitelist for apply, use flag prune-allowlist instead. (#120246, @pacoxu) [SIG CLI and Testing]

• Add CEL library for IP Addresses and CIDRs. This will not be available for use until 1.31. (#121912, @JoelSpeed) [SIG API Machinery]
• Added to MutableFeatureGate the ability to override the default setting of feature gates, to allow default-enabling a feature on a component-by-component basis instead of for all affected components simultaneously. (#122647, @benluddy) [SIG API Machinery and Cluster Lifecycle]
• Adds a rule on the kube_codegen tool to ignore vendor folder during the code generation. (#122729, @jparrill) [SIG API Machinery and Cluster Lifecycle]
• Allow users to mutate FSGroupPolicy and PodInfoOnMount in CSIDriver.Spec (#116209, @haoruan) [SIG API Machinery, Storage and Testing]
• Client-go events: NewEventBroadcasterAdapterWithContext should be used instead of NewEventBroadcasterAdapter if the goal is to support contextual logging. (#122142, @pohly) [SIG API Machinery, Instrumentation and Scheduling]
• Fixes accidental enablement of the new alpha optionalOldSelf API field in CustomResourceDefinition validation rules, which should only be allowed to be set when the CRDValidationRatcheting feature gate is enabled. (#122329, @jpbetz) [SIG API Machinery]
• Implement prescore extension point for volumeBinding plugin. Return skip if it doesn't do anything in Score. (#115768, @AxeZhan) [SIG Scheduling, Storage and Testing]
• Resource.k8s.io/ResourceClaim (alpha API): the strategic merge patch strategy for the status.reservedFor array was changed such that a strategic-merge-patch can add individual entries. This breaks clients using strategic merge patch to update status which rely on the previous behavior (replacing the entire array). (#122276, @pohly) [SIG API Machinery]
• When scheduling a mixture of pods using ResourceClaims and others which don't, scheduling a pod with ResourceClaims impacts scheduling latency less. (#121876, @pohly) [SIG API Machinery, Node, Scheduling and Testing]

• Add Timezone column in the output of kubectl get cronjob command (#122231, @ardaguclu) [SIG CLI]

• Add WatchListClient feature gate to client-go. When enabled it allows the client to get a stream of individual items instead of chunking from the server. (#122571, @p0lyn0mial) [SIG API Machinery]

• Add process_start_time_seconds to /metrics/slis endpoint of all components (#122750, @Richabanker) [SIG Architecture, Instrumentation and Testing]

• Adds exec-interactive-mode and exec-provide-cluster-info flags in kubectl config set-credentials command (#122023, @ardaguclu) [SIG CLI]

• Allow scheduling framework plugins that implement io.Closer to be gracefully closed. (#122498, @Gekko0114) [SIG Scheduling]

• Change --nodeport-addresses behavior to default to "primary node IP(s) only" rather than "all node IPs". (#122724, @nayihz) [SIG Network and Windows]

• Etcd: build image for v3.5.11 (#122233, @mzaian) [SIG API Machinery]

• Informers now support adding Indexers after the informer starts (#117046, @howardjohn) [SIG API Machinery]

• Introduce a feature gate mechanism to client-go. Depending on the actual implementation, users can control features via environmental variables or command line options. (#122555, @p0lyn0mial) [SIG API Machinery]

• Kube-scheduler implements scheduling hints for the NodeAffinity plugin. The scheduling hints allow the scheduler to only retry scheduling a Pod that was previously rejected by the NodeAffinity plugin if a new Node or a Node update matches the Pod's node affinity. (#122309, @carlory) [SIG Scheduling]

• Kube-scheduler implements scheduling hints for the NodeResourceFit plugin. The scheduling hints allow the scheduler to only retry scheduling a Pod that was previously rejected by the NodeResourceFit plugin if a new Node or a Node update matches the Pod's resource requirements or if an old pod update or delete matches the Pod's resource requirements. (#119177, @carlory) [SIG Scheduling]

• Kube-scheduler implements scheduling hints for the NodeUnschedulable plugin. The scheduling hints allow the scheduler to only retry scheduling a Pod that was previously rejected by the NodeSchedulable plugin if a new Node or a Node update sets .spec.unschedulable to false. (#122334, @carlory) [SIG Scheduling]

• Kube-scheduler implements scheduling hints for the PodTopologySpread plugin. The scheduling hints allow the scheduler to retry scheduling a Pod that was previously rejected by the PodTopologySpread plugin if create/delete/update a related Pod or a node which matches the toplogyKey. (#122195, @nayihz) [SIG Scheduling]

• Kubeadm: add better handling of errors during unmount when calling "kubeadm reset". When failing to unmount directories under "/var/run/kubelet", kubeadm will now throw an error instead of showing a warning and continuing to cleanup said directory. In such situations it is better for you to inspect the problem and resolve it manually, then you can call "kubeadm reset" again to complete the cleanup. (#122530, @neolit123) [SIG Cluster Lifecycle]

• Kubectl debug: add sysadmin profile (#119200, @eiffel-fl) [SIG CLI and Testing]

• Kubernetes is now built with Go 1.21.6 (#122705, @cpanato) [SIG Architecture, Release and Testing]

• Kubernetes is now built with go 1.22rc2 (#122889, @cpanato) [SIG Release and Testing]

• Print more information when kubectl describe a VolumeAttributesClass (#122640, @carlory) [SIG CLI]

• Promote KubeProxyDrainingTerminatingNodes to Beta (#122914, @alexanderConstantinescu) [SIG Network]

• Promote feature gate StableLoadBalancerNodeSet to GA (#122961, @alexanderConstantinescu) [SIG API Machinery, Cloud Provider and Network]

• Scheduler skips NodeAffinity Score plugin when NodeAffinity Score plugin has nothing to do with a Pod. You might notice an increase in the metric plugin_execution_duration_seconds for extension_point=score plugin=NodeAffinity, because the plugin will only run when the plugin is relevant (#117024, @sanposhiho) [SIG Scheduling and Testing]

• The option ignorable of scheduler extender can skip error both filter and bind. (#122503, @sunbinnnnn) [SIG Scheduling]

• Update kubedns and nodelocaldns to release version 1.22.28 (#121908, @mzaian) [SIG Cloud Provider]

• Update some interfaces' signature in scheduler:

  1. PluginsRunner: use NodeInfo in RunPreScorePlugins and RunScorePlugins.
  2. PreScorePlugin: use NodeInfo in PreScore.
  3. Extender: use NodeInfo in Filter and Prioritize. (#121954, @AxeZhan) [SIG Autoscaling, Node, Scheduling, Storage and Testing]

• When PreFilterResult filters out some Nodes, the scheduling framework assumes them as rejected via UnschedulableAndUnresolvable, that is those nodes won't be in the candidates of preemption process. Also, corrected how the scheduling framework handle Unschedulable status from PreFilter. Before this PR, if PreFilter return Unschedulable, it may result in an unexpected abortion in the preemption, which shouldn't happen in the default scheduler, but may happen in schedulers with a custom plugin. (#119779, @sanposhiho) [SIG Scheduling]

• kubectl describe: added Suspend to job, and Node-Selectors and Tolerations to pod template output (#122618, @ivanvc) [SIG CLI]

• A deprecated flag --pod-max-in-unschedulable-pods-duration was initially planned to be removed in v1.26, but we have to change this plan. We found an issue in which Pods can be stuck in the unschedulable pod pool for 5 min, and using this flag is the only workaround for this issue. This issue only could happen if you use custom plugins or if you change plugin set being used in your scheduler via the scheduler config. (#122013, @sanposhiho) [SIG Scheduling]
• Fix delete pod declare no controllor note. (#120159, @Ithrael) [SIG CLI]

• Add imagefs.inodesfree to default EvictionHard settings (#121834, @vaibhav2107) [SIG Node]

• Added metric name along with the utilization information when running kubectl get hpa (#122804, @sreeram-venkitesh) [SIG CLI]

• Allow deletion of pods that use raw block volumes on node reboot (#122211, @gnufied) [SIG Node and Storage]

• Changed the API server so that for admission webhooks that have a URL matching the hostname localhost, or a loopback IP address, the connection supports HTTP/2 where it can be negotiated. (#122558, @linxiulei) [SIG API Machinery and Testing]

• Etcd: Update to v3.5.11 (#122393, @mzaian) [SIG API Machinery, Cloud Provider, Cluster Lifecycle, Etcd and Testing]

• Fix Windows credential provider cannot find binary. Windows credential provider binary path may have ".exe" suffix so it is better to use LookPath() to support it flexibly. (#120291, @lzhecheng) [SIG Cloud Provider]

• Fix an issue where kubectl apply could panic when imported as a library (#122346, @Jefftree) [SIG CLI]

• Fix panic of Evented PLEG during kubelet start-up (#122475, @pacoxu) [SIG Node]

• Fix resource deletion failure caused by quota calculation error when InPlacePodVerticalScaling is turned on (#122701, @carlory) [SIG API Machinery, Node and Testing]

• Fix the following volume plugins may not create user visible files after kubelet was restarted.

  • configmap
  • secret
  • projected
  • downwardapi (#122807, @carlory) [SIG Storage]

• Fix: Ignore unnecessary node events and improve daemonset controller performance. (#121669, @xigang) [SIG Apps]

• Fix: Mount point may become local without calling NodePublishVolume after node rebooting. (#119923, @cvvz) [SIG Node and Storage]

• Fixed a bug where kubectl drain would consider a pod as having been deleted if an error occurs while calling the API. (#122574, @brianpursley) [SIG CLI]

• Fixed a regression since 1.24 in the scheduling framework when overriding MultiPoint plugins (e.g. default plugins). The incorrect loop logic might lead to a plugin being loaded multiple times, consequently preventing any Pod from being scheduled, which is unexpected. (#122068, @caohe) [SIG Scheduling]

• Fixed migration of in-tree vSphere volumes to the CSI driver. (#122341, @jsafrane) [SIG Storage]

• Fixes a race condition in the iptables mode of kube-proxy in 1.27 and later that could result in some updates getting lost (e.g., when a service gets a new endpoint, the rules for the new endpoint might not be added until much later). (#122204, @danwinship) [SIG Network]

• Fixes bug in ValidatingAdmissionPolicy which caused policies using CRD params to not successfully sync (#123003, @alexzielenski) [SIG API Machinery and Testing]

• For statically provisioned PVs, if its volume source is CSI type or it has migrated annotation, when it's deleted, the PersisentVolume controller won't changes its phase to the Failed state.

  With this patch, the external provisioner can remove the finalizer in next reconcile loop. Unfortunately if the provious existing pv has the Failed state, this patch won't take effort. It requires users to remove finalizer. (#122030, @carlory) [SIG Apps and Storage]

• If a pvc has an empty storageClassName, persistentvolume controller won't try to assign a default StorageClass (#122704, @carlory) [SIG Apps and Storage]

• Improves scheduler performance when no scoring plugins are defined. (#122058, @aleksandra-malinowska) [SIG Scheduling]

• Improves scheduler performance when no scoring plugins are defined. (#122435, @aleksandra-malinowska) [SIG Scheduling]

• Kube-proxy: fixed LoadBalancerSourceRanges not working for nftables mode (#122614, @tnqn) [SIG Network]

• Kubeadm: fix a regression in "kubeadm init" that caused a user-specified --kubeconfig file to be ignored. (#122735, @avorima) [SIG Cluster Lifecycle]

• Make decoding etcd's response respect the timeout context. (#121815, @HirazawaUi) [SIG API Machinery]

• QueueingHint implementation for NodeAffinity is reverted because we found potential scenarios where events that make Pods schedulable could be missed. (#122285, @sanposhiho) [SIG Scheduling]

• QueueingHint implementation for NodeUnschedulable is reverted because we found potential scenarios where events that make Pods schedulable could be missed. (#122288, @sanposhiho) [SIG Scheduling]

• Remove wrong warning event (FileSystemResizeFailed) during a pod creation if it uses a readonly volume and the capacity of the volume is greater or equal to its request storage. (#122508, @carlory) [SIG Storage]

• Reverts the EventedPLEG feature (beta, but disabled by default) back to alpha for a known issue (#122697, @pacoxu) [SIG Node]

• The scheduling queue didn't notice any extenders' failures, it could miss some cluster events, and it could end up Pods rejected by Extenders stuck in unschedulable pod pool in 5min in the worst-case scenario. Now, the scheduling queue notices extenders' failures and requeue Pods rejected by Extenders appropriately. (#122022, @sanposhiho) [SIG Scheduling]

• Use errors.Is() to handle err returned by LookPath() (#122600, @lzhecheng) [SIG Cloud Provider]

• ValidateVolumeAttributesClassUpdate also validates new vac object. (#122449, @carlory) [SIG Storage]

• When using a claim with immediate allocation and a pod referencing that claim couldn't get scheduled, the scheduler incorrectly may have tried to deallocate that claim. (#122415, @pohly) [SIG Node and Scheduling]

• Add warning for PV on relaim policy when it is Recycle (#122339, @carlory) [SIG Storage]
• Cleanup: remove getStorageAccountName warning messages (#121983, @andyzhangx) [SIG Cloud Provider and Storage]
• Client-go: Optimized leaders renewing leases by updating leader lock optimistically without getting the record from the apiserver first. Also added a new metric leader_election_slowpath_total that allow users to monitor how many leader elections are updated non-optimistically. (#122069, @linxiulei) [SIG API Machinery, Architecture and Instrumentation]
• Kube-proxy nftables mode is now compatible with kernel 5.4 (#122296, @tnqn) [SIG Network]
• Kubeadm: improve the overall logic, error handling and output messages when waiting for the kubelet and API server /healthz endpoints to return 'ok'. The kubelet and API server checks no longer run in parallel, but one after another (in serial). (#121958, @neolit123) [SIG Cluster Lifecycle]
• Kubeadm: show the supported shell types of 'kubeadm completion' in the error message when an invalid shell was specified (#122477, @SataQiu) [SIG Cluster Lifecycle]
• Kubeadm: use ttlSecondsAfterFinished to automatically clean up the upgrade-health-check Job that runs during upgrade preflighting. (#122079, @carlory) [SIG Cluster Lifecycle]
• Lock GA feature-gate ConsistentHTTPGetHandlers to default (#122578, @carlory) [SIG Node]
• Migrate client-go/metadata to contextual logging (#122225, @ricardoapl) [SIG API Machinery]
• Migrated the cmd/kube-proxy to use contextual logging. (#122197, @fatsheep9146) [SIG Network]
• Remove GA featuregate RemoveSelfLink (#122468, @carlory) [SIG API Machinery]
• Remove GA featuregate about ExperimentalHostUserNamespaceDefaultingGate in 1.30 (#122088, @bzsuni) [SIG Node]
• Remove GA featuregate about IPTablesOwnershipCleanup in 1.30 (#122137, @bzsuni) [SIG Network]
• Removed generally available feature gate ExpandedDNSConfig. (#122086, @bzsuni) [SIG Network]
• Removed generally available feature gate KubeletPodResourcesGetAllocatable. (#122138, @ii2day) [SIG Node]
• Removed generally available feature gate KubeletPodResources. (#122139, @bzsuni) [SIG Node]
• Removed generally available feature gate MinimizeIPTablesRestore. (#122136, @ty-dc) [SIG Network]
• Removed generally available feature gate ProxyTerminatingEndpoints. (#122134, @ty-dc) [SIG Network]
• Removed the deprecated azureFile in-tree storage plugin (#122576, @carlory) [SIG API Machinery, Cloud Provider, Node and Storage]
• Setting --cidr-allocator-type to CloudAllocator for kube-controller-manager will be removed in a future release. Please switch to and explore the options available in your external cloud provider (#123011, @dims) [SIG API Machinery and Network]
• The GA feature-gate APISelfSubjectReview is removed, and the feature is unconditionally enabled. (#122032, @carlory) [SIG Auth and Testing]
• The feature gate LegacyServiceAccountTokenTracking (GA since 1.28) is now removed, since the feature is unconditionally enabled. (#122409, @Rei1010) [SIG Auth]
• The in-tree cloud provider for azure has now been removed. Please use the external cloud provider and CSI driver from https://github.com/kubernetes/cloud-provider-azure instead. (#122857, @nilo19) [SIG API Machinery, Cloud Provider, Instrumentation, Node and Testing]
• The in-tree cloud provider for vSphere has now been removed. Please use the external cloud provider and CSI driver from https://github.com/kubernetes/cloud-provider-vsphere instead. (#122937, @dims) [SIG API Machinery, Cloud Provider, Storage and Testing]
• Update kube-dns to v1.22.27 (#121736, @ty-dc) [SIG Cloud Provider]
• Updated cni-plugins to v1.4.0. (#122178, @saschagrunert) [SIG Cloud Provider, Node and Testing]
• Updated cri-tools to v1.29.0. (#122271, @saschagrunert) [SIG Cloud Provider]

• sigs.k8s.io/knftables: v0.0.14

• github.com/go-logr/logr: v1.3.0 → v1.4.1
• github.com/go-logr/zapr: v1.2.3 → v1.3.0
• github.com/onsi/ginkgo/v2: v2.13.0 → v2.15.0
• github.com/onsi/gomega: v1.29.0 → v1.31.0
• github.com/opencontainers/runc: v1.1.10 → v1.1.11
• go.uber.org/atomic: v1.10.0 → v1.7.0
• go.uber.org/goleak: v1.2.1 → v1.3.0
• go.uber.org/zap: v1.19.0 → v1.26.0
• golang.org/x/crypto: v0.14.0 → v0.16.0
• golang.org/x/mod: v0.12.0 → v0.14.0
• golang.org/x/net: v0.17.0 → v0.19.0
• golang.org/x/sync: v0.3.0 → v0.5.0
• golang.org/x/sys: v0.13.0 → v0.15.0
• golang.org/x/term: v0.13.0 → v0.15.0
• golang.org/x/text: v0.13.0 → v0.14.0
• golang.org/x/tools: v0.12.0 → v0.16.1
• k8s.io/klog/v2: v2.110.1 → v2.120.1
• k8s.io/kube-openapi: 2dd684a → 778a556

• github.com/Azure/azure-sdk-for-go: v68.0.0+incompatible
• github.com/Azure/go-autorest/autorest/adal: v0.9.23
• github.com/Azure/go-autorest/autorest/date: v0.3.0
• github.com/Azure/go-autorest/autorest/mocks: v0.4.2
• github.com/Azure/go-autorest/autorest/to: v0.4.0
• github.com/Azure/go-autorest/autorest/validation: v0.3.1
• github.com/Azure/go-autorest/autorest: v0.11.29
• github.com/Azure/go-autorest/logger: v0.2.1
• github.com/Azure/go-autorest/tracing: v0.6.0
• github.com/Azure/go-autorest: v14.2.0+incompatible
• github.com/a8m/tree: 10a5fd5
• github.com/benbjohnson/clock: v1.1.0
• github.com/danwinship/knftables: v0.0.13
• github.com/dnaeon/go-vcr: v1.2.0
• github.com/dougm/pretty: 2ee9d74
• github.com/gofrs/uuid: v4.4.0+incompatible
• github.com/rasky/go-xdr: 4930550
• github.com/rubiojr/go-vhd: 02e2102
• github.com/vmware/govmomi: v0.30.6
• github.com/vmware/vmw-guestinfo: 25eff15