You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kubernetes supports and requires klog v2 in v1.19, so get ready to update/rewrite your log-watching tools when you eventually upgrade. This change to logging is the major step in implementing structured logging, which will allow folks to impement better log digestion tools and do less ad-hoc text parsing. This was also joined by a new feature in the dependency linter to ensure that klog v1 (or future libraries) do not accidentally be added back in.
A good reminder about race conditions between controllers, using Update or UpdateStatus calls in places where multiple controllers write to the same structure can lead to either failed writes or stomping on updates if you aren’t careful. Using a Patch request instead allows for more careful control over this, and in the future Server Side Apply will potentially allow for more direct detection of conflicts through field tracking.
The beta.kubernetes.io/os and beta.kubernetes.io/arch automatic node labels were deprecated back in 1.14 and have now been removed entirely. Make sure to check all your node selector and affinity settings to ensure they are using the kubernetes.io forms.
Other Merges
Kubelet metrics work on Windows nodes with init-containers present
Developer News
This Thursday is the May Community Meeting at 10am PDT/1700 UTC. SIGs Testing, UI, API Machinery, and Usability are presenting.
WG LTS wants to mark a year of patch support “implementable” based on the manifest fact that we are already supporting 1.16 for a year.
Release Schedule
Next Deadline: Enhancements Freeze, May 19th
Is your enhancement issue filed? Your KEP marked “implementable” and complete? It’s now, or wait for 1.20 (or file an exception).
All supported versions (1.16, 1.17, and 1.18) will be getting updated on Wednesday
Featured PRs
#90183: Update kubernetes to klog v2
Kubernetes supports and requires klog v2 in v1.19, so get ready to update/rewrite your log-watching tools when you eventually upgrade. This change to logging is the major step in implementing structured logging, which will allow folks to impement better log digestion tools and do less ad-hoc text parsing. This was also joined by a new feature in the dependency linter to ensure that klog v1 (or future libraries) do not accidentally be added back in.
#90978: Changed scheduler to use patch when updating pod status
A good reminder about race conditions between controllers, using Update or UpdateStatus calls in places where multiple controllers write to the same structure can lead to either failed writes or stomping on updates if you aren’t careful. Using a Patch request instead allows for more careful control over this, and in the future Server Side Apply will potentially allow for more direct detection of conflicts through field tracking.
#91046: kubelet no longer registers “beta.kubernetes.io/os” and “beta.kubernetes.io/arch” node labels to apiserver
The
beta.kubernetes.io/os
andbeta.kubernetes.io/arch
automatic node labels were deprecated back in 1.14 and have now been removed entirely. Make sure to check all your node selector and affinity settings to ensure they are using thekubernetes.io
forms.Other Merges
/livez
and/readyz
endpoints separately instead of relying on/healthz
NodeResourcesLeastAllocated
andNodeResourcesMostAllocated
pluginsDeprecated
kubelet\_certificate\_manager\_client\_ttl\_seconds
replaces the non-functionalkubelet\_certificate\_manager\_client\_expiration\_seconds
beta.kubernetes.io/os
andbeta.kubernetes.io/arch
node labels are deprected, to be removed in 1.22 (back-ported to all versions)--really-crash-for-testing
and--chaos-chance
testing flags have been removed from the kubelet, which is a shame, because they sound like they would have been real fun in productionVersion Updates
The text was updated successfully, but these errors were encountered: