- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for eg (0.21 sec)
-
CHANGELOG/CHANGELOG-1.28.md
### Other (Cleanup or Flake) - Kube-controller-manager and cloud-controller-manager have changed the name of controllers that can be turned off/on that are passed to the `--controllers` flag (eg `pod-garbage-collector-controller` ). The old names (eg `podgc`) are also accepted and aliased to the new names ([#115813](https://github.com/kubernetes/kubernetes/pull/115813), [@atiratree](https://github.com/atiratree)) [SIG API Machinery and Cloud Provider]
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.4.md
- **Simplified User Experience** - Easier to get a cluster up and running (eg: `kubeadm`, intra-cluster bootstrapping) - Easier to understand a cluster (eg: API audit logs, server-based API defaults) - **Stateful Application Support** - Enhanced persistence capabilities (eg: `StorageClasses`, new volume plugins) - New resources and scheduler features (eg: `ScheduledJob` resource, pod/node affinity/anti-affinity) - **Cluster Federation**
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Thu Dec 24 02:28:26 GMT 2020 - 133.5K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.20.md
- In dual-stack bare-metal clusters, you can now pass dual-stack IPs to `kubelet --node-ip`. eg: `kubelet --node-ip 10.1.0.5,fd01::0005`. This is not yet supported for non-bare-metal clusters. In dual-stack clusters where nodes have dual-stack addresses, hostNetwork pods
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) -
CHANGELOG/CHANGELOG-1.15.md
- kube-proxy no longer automatically cleans up network rules created by running kube-proxy in other modes. If you are switching the kube-proxy mode (EG: iptables to IPVS), you will need to run `kube-proxy --cleanup`, or restart the worker node (recommended) before restarting kube-proxy. If you are not switching kube-proxy between different modes, this change should not require any action. ([#76109...
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Thu May 05 13:44:43 GMT 2022 - 278.9K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.14.md
* kube-proxy no longer automatically cleans up network rules created by running kube-proxy in other modes. If you are switching the mode that kube-proxy is in running in (EG: iptables to IPVS), you will need to run `kube-proxy --cleanup`, or restart the worker node (recommended) before restarting kube-proxy. ([#76109](https://github.com/kubernetes/kubernetes/pull/76109), [@vllry](https://github.com/vllry))
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Mon Jun 14 22:06:39 GMT 2021 - 271.5K bytes - Viewed (0)