…From the perspective of the Cluster API maintainers, in-place updates are most useful for making changes that don't otherwise require a node drain or pod restart; for example: changing user…
…the API versioning policy . An example of this is the Deployment resource. This was introduced under the extensions/v1beta1 group in 1.6 and as the project changed has been promoted to…
…or to ServiceAccounts - never to individual users. The broker or identity provider then adds or removes users from that group as needed. The broker can also enforce extra policy on top, like…
…Bound service account token improvement The inclusion of the node name in the service account token claims allows users to use such information during authorization and admission (ValidatingAdmissionPolicy). Furthermore this improvement keeps…
…Skip Volume Ownership change graduates to GA The feature to configure volume permission and ownership change policy for Pods moved to GA in 1.23. This allows users to skip recursive permission…
…PreferClose traffic distribution is deprecated The spec.trafficDistribution field within a Kubernetes Service allows users to express preferences for how traffic should be routed to Service endpoints. KEP-3015 deprecates PreferClose and…
…This meant changing them required deleting and recreating the entire Pod. For stateful services, batch jobs, or latency-sensitive workloads, this was an incredibly disruptive operation. In-Place Pod Resize makes CPU…
To show you the most relevant results, we’ve omitted some entries very similar to those already shown. Repeat the search with the omitted results included.