- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for IPv4 (0.19 sec)
-
CHANGELOG/CHANGELOG-1.29.md
- `kubelet` allows pods to use the `net.ipv4.tcp_fin_timeout`, “net.ipv4.tcp_keepalive_intvl” and “net.ipv4.tcp_keepalive_probes“ sysctl by default; Pod Security Admission allows this sysctl in `v1.29+` versions of the baseline and restricted policies. ([#121240](https://github.com/kubernetes/kubernetes/pull/121240), [@HirazawaUi](https://github.com/HirazawaUi)) - `kubelet` now allows pods to use the `net.ipv4.tcp_keepalive_time` sysctl by default
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Oct 23 04:37:31 UTC 2024 - 375.1K bytes - Viewed (1) -
manifests/charts/base/files/crd-all.gen.yaml
to other services in the mesh. items: properties: bind: description: The IP(IPv4 or IPv6) or the Unix domain socket to which the listener should be bound to. type: string captureMode: description: |-
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri Nov 01 16:23:52 UTC 2024 - 805K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.32.md
- Allow pods to use the `net.ipv4.tcp_rmem` and `net.ipv4.tcp_wmem` sysctl by default when the kernel version is 4.15 or higher. With the kernel 4.15 the sysctl became namespaced.
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Tue Oct 29 20:17:52 UTC 2024 - 121.6K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.28.md
- Fixed a regression in kube-proxy where it might refuse to start if given single-stack IPv6 configuration options on a node that has both IPv4 and IPv6 IPs. ([#121008](https://github.com/kubernetes/kubernetes/pull/121008), [@danwinship](https://github.com/danwinship)) [SIG Network]
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Oct 23 04:34:59 UTC 2024 - 456.9K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.31.md
- Added support to the kube-proxy nodePortAddresses / --nodeport-addresses option to accept the value "primary", meaning to only listen for NodePort connections on the node's primary IPv4 and/or IPv6 address (according to the Node object). This is strongly recommended, if you were not previously using --nodeport-addresses, to avoid surprising behavior.
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Oct 23 12:18:32 UTC 2024 - 315.4K bytes - Viewed (0)