Kubernetes v1.27.0-alpha1 is live!

17 views
Skip to first unread message

Cici Huang

unread,
Jan 24, 2023, 5:56:46 PM1/24/23
to d...@kubernetes.io, kubernete...@kubernetes.io
Kubernetes Community,

Kubernetes v1.27.0-alpha.1 has been built and pushed using Golang version 1.19.5.

The release notes have been updated in CHANGELOG-1.27.md, with a pointer to them on GitHub:


v1.27.0-alpha.1

Downloads for v1.27.0-alpha.1

Source Code

filenamesha512 hash
kubernetes.tar.gz36ddbb7f1cdf386cd6857d891029b7244dd13aa346a78ba2fa2146b866751802989fc5c5c8a8675f80b72b12816ae94b2b00fdeb01421ef15aad8ae87c06c512
kubernetes-src.tar.gzd5be5bdf5734c89338b2fd52942b70f8d57d831659235a0ea91c6fb10d74637c2a2aeed602bdafb4da01071764f754ddec9d37abf8aeb8eaa11636e405e93b04

Client Binaries

filenamesha512 hash
kubernetes-client-darwin-amd64.tar.gzd9b5f7ec09b64a6e0d270c077fdcd4835b6e16f39373fbf1a2e2526f80aa4df25f41a7e1dab1c33c4ec3f3c430b1cd42b08944d4c39d8ac78c4b23db83d6411b
kubernetes-client-darwin-arm64.tar.gze1a0f33d0610dbac940db0cad930bf4530f90a9c1702e534bb8c5524077af82d6da2f63befd3ba331ddfe84710ece101b9dd93f308ef727605646cc0d0847292
kubernetes-client-linux-386.tar.gz1e49e5f94a3bd14c6c5681ea8ad003948f7824566dc4d8ff299aed0a3e650a2b0674ade00fc951131fe34c210b8b7832c1a1fd5c290ee8c9e42bac89efdc8f26
kubernetes-client-linux-amd64.tar.gzddb000a6a1604a5cb95bbe296366eebd9e0b9b4be250b0d22302c697294840c216641f287dc7212b49f9f121549172590a1f1e285b3d87cee32bcbd95a7d19b1
kubernetes-client-linux-arm.tar.gz40c242c7bae26da4948fe97daf256dc48d99edc91a535ff9f4516e214ff50cfbbbc985be8e4361a97bfd54dc8b406e6f4a68b1054396b01a157d54a6bd82c7e3
kubernetes-client-linux-arm64.tar.gz54954248f4aa1d2977fe92a552cf7e0298c94adac8bf0720c697cfce654a1fbdf01cd56219e0dd064bab7b07a4cd125c257b61cd4d69af03ec550aec31cb26ac
kubernetes-client-linux-ppc64le.tar.gzd58709ea83b2a82ea44ae402a574ddc97177494bac90b9c6de30caf3fbcc79697addd0bb8245a62bbaf2fd35483415293659703cbed573bbe11a86a57814f8a3
kubernetes-client-linux-s390x.tar.gz08ab82af97bb2ccf0b90d5de23960ce2634a42eaafcc50725ce345e3df61e082acc2e733c3aae159463645cbad28a8536371850899403eaeb7a040ed221ba861
kubernetes-client-windows-386.tar.gz047fdddf4c1095240eb1296a1d79e9dbb90325d13e9ed94b3532ecfa843dbd089b4b5aa3d6a51e4265c1ecdb2f08b73cd05f309b8bf4c585b213fa605a0bc74d
kubernetes-client-windows-amd64.tar.gz1bd72cfd091f452b4d32496a1f1b0c78231ae6cf9696ca029a340761aaeba08e27003d9fcb5942a63b2feddb2562b287b0d8c49fb0d92f2e50b65a947591b105
kubernetes-client-windows-arm64.tar.gz07daf9e21a7741908e358f0a9ae30164229344c1653c435fb1c6029932431e5bb985842ebcc97330a6ca5aff57584488a17fe01b234de6286f6753faaa4d31f3

Server Binaries

filenamesha512 hash
kubernetes-server-linux-amd64.tar.gzd426504774023346a994ca709ae48daf47baf0e2f680a2237cc1b8b5b2ba7d4a41be9d0f80af4f1c097348b01a3e1a968b3bbea5cb5937d17e0ef23db6a36b27
kubernetes-server-linux-arm.tar.gzd4b4eaa2012b9ce5f3fa111cd1a61ef98aec238905f134636470bab2661d4c14464dfc8223bd74456a8848e3c7fe879d14e1eba6c4f2376f9042893077fcb068
kubernetes-server-linux-arm64.tar.gzbc9b1388a93c65f6b603271e8a1a1d622698fd54ce26d3743e888efd5f61cd538229161006a2ab5afcbda8782f87646c9da02a5e7cc93ff52e48616a7d56cb33
kubernetes-server-linux-ppc64le.tar.gz69972b9c95b50b7566660b44547d974133e6f2f18737a93c2f4a6ca5833400473c0917c0c44b1a27336990214c1f188c75e39701d91c567b8ff7d8ccd3496243
kubernetes-server-linux-s390x.tar.gz1867d483df955260b9cf13bfe43451c2f906c1854399a396e0d9e2fac33fc4343d3c79039891c1b943cf4707312cedcffb4d0cedf7a69271020f88c50d230d5d

Node Binaries

filenamesha512 hash
kubernetes-node-linux-amd64.tar.gz132c74737e8fd525c8a4bcedbf7ad783917a42a485e740586933dceef76177c6043682654f76f88670933fea0a3066adfcfdd08a9b6e07b3a6ad23e903c1b4a5
kubernetes-node-linux-arm.tar.gz7d7716457ff136344e8338ad52e819346de13495d79a5c615a8bfc9d45a00fa659d60630aa2025d8bc4570080d77d1e298e47a8934d47c0c3fb5b70b043ef2dd
kubernetes-node-linux-arm64.tar.gzdf5b9d5ae99d8001b25448bf6148b9cf3a47ce8b4d1f7b1f52ab3dd8ad0ee6958045a382a561d3a617991a2255712f2e6ed0c8d6fb843edbdd0284054a238d74
kubernetes-node-linux-ppc64le.tar.gz9c0fc5952d8dcf07cb0225c252112fead50a4920d978f174a17a881d92c8b34ed162ec3a806bb451a990b81e8294f39755c93acbfd6147748c5dea9bb8ad38f2
kubernetes-node-linux-s390x.tar.gz0b203edad11a1350d3f3b6f16391450f2ca7bb19424a9eb398f69f8ef2195c821d3c72105248889cfb6efd317a3012d94c9564cb6b5794ba050fcc0902364eaa
kubernetes-node-windows-amd64.tar.gz68b2d73b7bf98445498e46188d39fde06acfee946ac9075f064f39bc7ea658cfcb82498ffe06bc2a2272ad5c105cac21d4929de47038e0ce95e07e3cd9d519ad

Container Images

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.

namearchitectures
registry.k8s.io/conformance:v1.27.0-alpha.1amd64armarm64ppc64les390x
registry.k8s.io/kube-apiserver:v1.27.0-alpha.1amd64armarm64ppc64les390x
registry.k8s.io/kube-controller-manager:v1.27.0-alpha.1amd64armarm64ppc64les390x
registry.k8s.io/kube-proxy:v1.27.0-alpha.1amd64armarm64ppc64les390x
registry.k8s.io/kube-scheduler:v1.27.0-alpha.1amd64armarm64ppc64les390x

Changelog since v1.26.0

Changes by Kind

Deprecation

  • Add warnings to the Services API. Kubernetes now warns for Services in the case of:
    • IPv4 addresses with leading zeros
    • IPv6 address in non-canonical format (RFC 5952) (#114505@aojea) [SIG Network]
  • Support for the alpha seccomp annotations seccomp.security.alpha.kubernetes.io/pod and container.seccomp.security.alpha.kubernetes.io, deprecated since v1.19, has been completely removed. The seccomp fields are no longer auto-populated when pods with seccomp annotations are created. Pods should use the corresponding pod or container securityContext.seccompProfile field instead. (#114947@saschagrunert)

API Change

  • A terminating pod on a node that is not caused by preemption won't prevent kube-scheduler from preempting pods on that node
    • Rename 'PreemptionByKubeScheduler' to 'PreemptionByScheduler' (#114623@Huang-Wei) [SIG Scheduling]
  • Added new option to the InterPodAffinity scheduler plugin to ignore existing pods` preferred inter-pod affinities if the incoming pod has no preferred inter-pod affinities. This option can be used as an optimization for higher scheduling throughput (at the cost of an occasional pod being scheduled non-optimally/violating existing pods' preferred inter-pod affinities). To enable this scheduler option, set the InterPodAffinity scheduler plugin arg "ignorePreferredTermsOfExistingPods: true". (#114393@danielvegamyhre) [SIG API Machinery and Scheduling]
  • Added warnings about workload resources (Pods, ReplicaSets, Deployments, Jobs, CronJobs, or ReplicationControllers) whose names are not valid DNS labels. (#114412@thockin) [SIG API Machinery and Apps]
  • K8s.io/component-base/logs: usage of the pflag values in a normal Go flag set led to panics when printing the help message (#114680@pohly) [SIG Instrumentation]
  • Kube-proxy, kube-scheduler and kubelet have HTTP APIs for changing the logging verbosity at runtime. This now also works for JSON output. (#114609@pohly) [SIG API Machinery, Architecture, Cloud Provider, Instrumentation and Testing]
  • Kubeadm: explicitly set priority for static pods with priorityClassName: system-node-critical (#114338@champtar) [SIG Cluster Lifecycle]
  • Kubelet: migrate "--container-runtime-endpoint" and "--image-service-endpoint" to kubelet config (#112136@pacoxu) [SIG API Machinery, Node and Scalability]
  • Kubernetes components that perform leader election now only support using Leases for this. (#114055@aimuz) [SIG API Machinery, Cloud Provider and Scheduling]
  • StatefulSet names must be DNS labels, rather than subdomains. Any StatefulSet which took advantage of subdomain validation (by having dots in the name) can't possibly have worked, because we eventually set pod.spec.hostname from the StatefulSetName, and that is validated as a DNS label. (#114172@thockin) [SIG Apps]
  • The following feature gates for volume expansion GA features have been removed and must no longer be referenced in --feature-gates flags: ExpandCSIVolumes, ExpandInUsePersistentVolumes, ExpandPersistentVolumes (#113942@mengjiao-liu) [SIG API Machinery, Apps and Testing]
  • The list-type of the alpha resourceClaims field introduced to Pods in 1.26.0 was modified from "set" to "map", resolving an incompatibility with use of this schema in CustomResourceDefinitions and with server-side apply. (#114585@JoelSpeed) [SIG API Machinery]

Feature

  • Graduated the LegacyServiceAccountTokenTracking feature gate to Beta. The usage of auto-generated secret-based service account token now produces warnings by default, and relevant Secrets are labeled with a last-used timestamp (label key kubernetes.io/legacy-token-last-used). (#114523@zshihang) [SIG API Machinery and Auth]
  • Kube-proxy accepts the ContextualLogging, LoggingAlphaOptions, LoggingBetaOptions feature gates. (#115233@pohly) [SIG Instrumentation and Network]
  • Kube-up now includes CoreDNS version v1.9.3 (#114279@pacoxu) [SIG Cloud Provider and Cluster Lifecycle]
  • Kubeadm: add the experimental (alpha) feature gate EtcdLearnerMode that allows etcd members to be joined as learner and only then promoted as voting members (#113318@pacoxu) [SIG Cluster Lifecycle]
  • Kubectl will display SeccompProfile for pods, containers and ephemeral containers, if values were set. (#113284@williamyeh) [SIG CLI and Security]
  • Kubectl: add e2e test for default container annotation (#115046@pacoxu) [SIG Architecture, CLI and Testing]
  • Kubelet TCP and HTTP probes are more effective using networking resources: conntrack entries, sockets, ... This is achieved by reducing the TIME-WAIT state of the connection to 1 second, instead of the defaults 60 seconds. This allows kubelet to free the socket, and free conntrack entry and ephemeral port associated. (#115143@aojea) [SIG Network and Node]
  • Kubernetes is now built with Go 1.19.5 (#115010@cpanato) [SIG Release and Testing]
  • Make kubectl-convert binary linking static (also affects the deb and rpm packages). (#114228@saschagrunert) [SIG Release]
  • New metrics cidrset_cidrs_max_total and multicidrset_cidrs_max_total expose the max number of CIDRs that can be allocated. (#112260@aryan9600) [SIG Apps, Instrumentation and Network]
  • Profiling can now be served on a unix-domain socket by using the --profiling-path option (when profiling is enabled) for security purposes. (#114191@apelisse) [SIG API Machinery]
  • Scheduler doesn't run plugin's Filter method when its PreFilter method returned a Skip status. In other words, your PreFilter/Filter plugin can return a Skip status in PreFilter if the plugin does nothing in Filter for that Pod. Scheduler skips NodeAffinity Filter plugin when NodeAffinity Filter plugin has nothing to do with a Pod. It may affect some metrics values related to the NodeAffinity Filter plugin. (#114125@sanposhiho) [SIG Scheduling, Storage and Testing]
  • Scheduler skips InterPodAffinity Filter plugin when InterPodAffinity Filter plugin has nothing to do with a Pod. It may affect some metrics values related to the InterPodAffinity Filter plugin. (#114889@sanposhiho) [SIG Scheduling and Testing]
  • Scheduler volumebinding: leverage PreFilterResult to reduce down to only eligible node(s) for pod with bound claim(s) to local PersistentVolume(s) (#109877@yibozhuang) [SIG Scheduling, Storage and Testing]
  • The MinDomainsInPodTopologySpread feature gate is enabled by default as a Beta feature in 1.27. (#114445@mengjiao-liu) [SIG Scheduling]
  • The AdvancedAuditing feature gate was locked to true in v1.27, and will be removed completely in v1.28 (#115163@SataQiu) [SIG API Machinery]
  • Updated cAdvisor to v0.47.0 (#114883@bobbypage) [SIG Architecture, Auth, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Node and Storage]
  • Use HorizontalPodAutoscaler v2 for kubectl (#114886@a7i) [SIG CLI]
  • Verify that the key matches the cert (#113581@aimuz) [SIG Apps]
  • When any scheduler plugin returns an unschedulableAndUnresolvable status in PostFilter, the scheduling cycle terminates immediately for that Pod. (#114699@kerthcet) [SIG Scheduling and Testing]

Documentation

  • Error message for Pods with requests exceeding limits will have a limit value printed. (#112925@SergeyKanzhelev) [SIG Apps and Node]

Failing Test

  • Deflake a preemption test that may patch Nodes incorrectly. (#114350@Huang-Wei) [SIG Scheduling and Testing]

Bug or Regression

  • Adding (dry run) and (server dry run) suffixes to kubectl scale command when dry-run is passed (#114252@ardaguclu) [SIG CLI and Testing]
  • Change the error message to "cannot exec into multiple objects at a time" when file passed to kubectl exec contains multiple resources (#114249@ardaguclu) [SIG CLI and Testing]
  • Changing the error message of kubectl rollout restart when subsequent kubectl rollout restart commands are executed within a second (#113040@ardaguclu) [SIG CLI]
  • Client-go: fixes potential data races retrying requests using a custom io.Reader body; with this fix, only requests with no body or with string / []byte / runtime.Object bodies can be retried (#113933@liggitt) [SIG API Machinery]
  • Do not add DisruptionTarget condition by PodGC for pods which are in terminal phase (#115056@mimowo) [SIG Apps and Testing]
  • Do not include preemptor pod metadata in the event message (#114923@mimowo) [SIG Scheduling]
  • Do not include preemptor pod metadata in the message of DisruptionTarget condition (#114914@mimowo) [SIG Scheduling]
  • Do not include scheduler name in the preemption event message (#114980@mimowo) [SIG Scheduling]
  • Don't create endpoints for Service of type ExternalName. (#114814@panslava) [SIG Apps, Network and Testing]
  • Fail CRI connection if service or image endpoint is throwing any error on kubelet startup. (#115102@saschagrunert) [SIG Node]
  • Failed pods associated with a job with parallelism = 1 are recreated by the job controller honoring exponential backoff delay again. However, for jobs with parallelism > 1, pods might be created without exponential backoff delay. (#114516@nikhita) [SIG Apps and Testing]
  • Fix SELinux label for host path volumes created by host path provisioner (#112021@mrunalp) [SIG Node and Storage]
  • Fix a bug on the endpointslice mirroring controller that generated multiple slices in some cases for custom endpoints in non canonical format (#114155@aojea) [SIG Apps, Network and Testing]
  • Fix a bug where events/v1 Events with similar event type and reporting instance were not aggregated by client-go. (#112365@dgrisonnet) [SIG API Machinery and Instrumentation]
  • Fix a bug where when emitting similar Events consecutively, some were rejected by the apiserver. (#114237@dgrisonnet) [SIG API Machinery]
  • Fix a data race when emitting similar Events consecutively (#114236@dgrisonnet) [SIG API Machinery]
  • Fix a regression that the scheduler always goes through all Filter plugins. (#114518@Huang-Wei) [SIG Scheduling]
  • Fix bug in CRD Validation Rules (beta) and ValidatingAdmissionPolicy (alpha) where all admission requests could result in internal error: runtime error: index out of range [3] with length 3 evaluating rule: <rule name> under certain circumstances. (#114857@jpbetz) [SIG API Machinery, Auth and Cloud Provider]
  • Fix clearing of rate-limiter for the queue of checks for cleaning stale pod disruption conditions. The bug could result in the PDB synchronization updates firing too often or the pod disruption cleanups taking too long to happen. (#114770@mimowo) [SIG Apps]
  • Fix: Route controller should update routes with NodeIP changed (#108095@lzhecheng) [SIG Cloud Provider and Network]
  • Fixed CSI PersistentVolumes to allow Secrets names longer than 63 characters. (#114776@jsafrane) [SIG Apps]
  • Fixed DaemonSet to update the status even if it fails to create a pod. (#113787@gjkim42) [SIG Apps and Testing]
  • Fixed StatefulSetAutoDeletePVC feature when OwnerReferencesPermissionEnforcement admission plugin is enabled. (#114116@jsafrane) [SIG Apps, Auth and Storage]
  • Fixed bug in reflector that couldn't recover from "Too large resource version" errors with API servers before 1.17.0 (#115093@xuzhenglun) [SIG API Machinery]
  • Fixed file permission issues that happened during update of Secret/ConfigMap/projected volume when fsGroup is used. The problem caused a race condition where application gets intermittent permission denied error when reading files that were just updated, before the correct permissions were applied. (#114464@tsaarni) [SIG Storage]
  • Fixes panic validating custom resource definition schemas that set multipleOf to 0 (#114869@liggitt) [SIG API Machinery, Architecture, Auth, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Node and Storage]
  • Fixes stuck apiserver if an aggregated apiservice returned 304 Not Modified for aggregated discovery information (#114459@alexzielenski) [SIG API Machinery]
  • Fixing issue in Winkernel Proxier - Unexpected active TCP connection drops while horizontally scaling the endpoints for a LoadBalancer Service with Internal Traffic Policy: Local (#113742@princepereira) [SIG Network and Windows]
  • Fixing issue on Windows when calculating cpu limits on nodes with more than 64 logical processors (#114231@mweibel) [SIG Node and Windows]
  • Fixing issue with Winkernel Proxier - No ingress load balancer rules with endpoints to support load balancing when all the endpoints are terminating. (#113776@princepereira) [SIG Network, Testing and Windows]
  • Hide .metadata.managedFields when describing CRs (#114584@soltysh) [SIG CLI]
  • IPVS: Any ipvs scheduler can now be configured. If a un-usable scheduler is configured kube-proxy will re-start and the logs must be checked (same as before but different log printouts). (#114878@uablrek) [SIG Network]
  • If a user attempts to add an ephemeral container to a static pod, they will get a visible validation error. (#114086@xmcqueen) [SIG Apps and Node]
  • Kube-apiserver: removed N^2 behavior loading webhook configurations. (#114794@lavalamp) [SIG API Machinery, Architecture, CLI, Cloud Provider and Node]
  • Kube-controller-manager will not run nodeipam controller when allocator type is CloudAllocator and the cloud provider is not enabled. (#114596@andrewsykim) [SIG Cloud Provider]
  • Kube-proxy with proxy-mode=ipvs can be used with statically linked kernels. The reseved IPv4 range TEST-NET-2 in rfc5737 MUST NOT be used for ClusterIP or loadBalancerIP since address 198.51.100.0 is used for probing. (#114669@uablrek) [SIG Network]
  • Kubeadm: fix the bug that kubeadm always do CRI detection even if it is not required by a phase subcommand (#114455@SataQiu) [SIG Cluster Lifecycle]
  • Kubeadm: improve retries when updating node information, in case kube-apiserver is temporarily unavailable (#114176@QuantumEnergyE) [SIG Cluster Lifecycle]
  • Kubeadm: respect user provided kubeconfig during discovery process (#113998@SataQiu) [SIG Cluster Lifecycle]
  • Kubectl port-forward now exits with exit code 1 when remote connection is lost (#114460@brianpursley) [SIG API Machinery]
  • Kubectl: use label selector for filtering out resources when pruning for kubectl diff (#114863@danlenar) [SIG CLI and Testing]
  • LabelSelectors specified in topologySpreadConstraints are now validated to ensure that pod is scheduled as expected. Existing pods with invalid LabelSelectors can be updated, but new pods are required to specify valid LabelSelectors. (#111802@maaoBit) [SIG Apps]
  • Optimizing loadbalancer creation with the help of attribute Internal Traffic Policy: Local (#114407@princepereira) [SIG Network]
  • Relax API validation for usage key encipherment and kubelet uses requested usages accordingly (#111660@pacoxu) [SIG API Machinery, Apps, Auth and Node]
  • Shared informers now correctly propagate whether they are synced or not. Individual informer handlers may now check if they are synced or not (new HasSynced method). Library support is added to assist controllers in tracking whether their own work is completed for items in the initial list (AsyncTracker). (#113985@lavalamp) [SIG API Machinery, Apps, Auth, Network, Node and Testing]
  • Statefulset status will be consistent on API errors (#113834@atiratree) [SIG Apps]
  • Total test spec is now available by ProgressReporter, it will be reported before test suite got executed. (#114417@chendave) [SIG Architecture, Auth, CLI, Cloud Provider, Instrumentation, Node and Testing]
  • TryUnmount should respect mounter.withSafeNotMountedBehavior (#114736@andyzhangx) [SIG Storage]
  • When describing deployments, OldReplicaSets now always shows all replicasets controlled the deployment, not just those that still have replicas available. (#113083@llorllale) [SIG CLI]

Other (Cleanup or Flake)

  • Callers of wait.ExponentialBackoffWithContext must pass a ConditionWithContextFunc to be consistent with the signature and avoid creating a duplicate context. If your condition does not need a context you can use the ConditionFunc.WithContext() helper to ignore the context, or use ExponentialBackoff directly. (#115113@smarterclayton) [SIG API Machinery, Storage and Testing]
  • Fix incorrect log information (#110723@yangjunmyfm192085) [SIG Network]
  • Improved misleading message, in case of no metrics received for the HPA controlled pods. (#114740@kushagra98) [SIG Apps and Autoscaling]
  • Kubeadm: remove the deprecated v1beta2 API. kubeadm 1.26's "config migrate" command can be used to migrate a v1beta2 configuration file to v1beta3. (#114540@pacoxu) [SIG Cluster Lifecycle]
  • Remove unused rule for nodes/spec from ClusterRole system:kubelet-api-admin (#113267@hoskeri) [SIG Auth and Cloud Provider]
  • Renamed API server identity Lease labels to use the key apiserver.kubernetes.io/identity (#114586@andrewsykim) [SIG API Machinery, Apps, Cloud Provider and Testing]
  • The CSIMigrationAzureFile feature gate (for the feature which graduated to GA in v1.26) is now unconditionally enabled and will be removed in v1.28. (#114953@enj) [SIG Storage]
  • The WaitFor and WaitForWithContext functions in the wait package have been marked private. Callers should use the equivalent Poll* method with a zero duration interval. (#115116@smarterclayton) [SIG API Machinery]
  • The feature gates CSIInlineVolumeCSIMigrationDaemonSetUpdateSurgeEphemeralContainersIdentifyPodOSLocalStorageCapacityIsolationNetworkPolicyEndPort and StatefulSetMinReadySeconds that graduated to GA in v1.25 and were unconditionally enabled have been removed in v1.27 (#114410@SataQiu) [SIG Node]
  • This flag master-service-namespace will be removed in v1.27. (#114446@lengrongfu) [SIG API Machinery]
  • Wait.ContextForChannel() now implements the context.Context interface and does not return a cancellation function. (#115140@smarterclayton) [SIG API Machinery and Cloud Provider]

Dependencies

Added

Changed

Removed



Contributors, the CHANGELOG-1.27.md has been bootstrapped with v1.27.0-alpha.1 release notes and you may edit now as needed.



Published by your Kubernetes Release Managers.

Reply all
Reply to author
Forward
0 new messages