- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for Leicht (0.26 sec)
-
common-protos/k8s.io/api/core/v1/generated.proto
// (i.e. it's a no-op). A null preferred scheduling term matches no objects (i.e. is also a no-op). message PreferredSchedulingTerm { // Weight associated with matching the corresponding nodeSelectorTerm, in the range 1-100. optional int32 weight = 1; // A node selector term, associated with the corresponding weight. optional NodeSelectorTerm preference = 2; }
Plain Text - Registered: Wed May 01 22:53:12 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 255.8K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.28.md
- Kube-proxy service health returns http header `X-Load-Balancing-Endpoint-Weight` with number of local endpoints. The same information is still available in response body JSON `payload.LocalEndpoints`. ([#118999](https://github.com/kubernetes/kubernetes/pull/118999), [@cezarygerard](https://github.com/cezarygerard))
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Apr 16 20:44:48 GMT 2024 - 385.1K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.23.md
- Introduce `v1beta3` API for scheduler. This version - increases the weight of user specifiable priorities. The weights of following priority plugins are increased - `TaintTolerations` to 3 - as leveraging node tainting to group nodes in the cluster is becoming a widely-adopted practice
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Feb 28 21:06:52 GMT 2023 - 424.5K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.22.md
- The deprecated flag `--hard-pod-affinity-symmetric-weight` and `--scheduler-name` have been removed from `kube-scheduler`. Use `ComponentConfig` instead to configure those parameters. ([#102805](https://github.com/kubernetes/kubernetes/pull/102805), [@ahg-g](https://github.com/ahg-g))
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Tue Dec 13 12:43:45 GMT 2022 - 454.1K bytes - Viewed (1) -
CHANGELOG/CHANGELOG-1.20.md
Previously, for IPv6, if the podSubnet had a mask lower than /112, kubeadm calculated a node-mask to be multiple of eight and splitting the available bits to maximise the number used for nodes. ([#95723](https://github.com/kubernetes/kubernetes/pull/95723), [@aojea](https://github.com/aojea)) [SIG Cluster Lifecycle]
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Wed Jan 19 21:05:45 GMT 2022 - 409K bytes - Viewed (0)