- Sort Score
- Result 10 results
- Languages All
Results 21 - 23 of 23 for NodeIPs (0.18 sec)
-
pkg/kubelet/kubelet_node_status.go
if kl.cloud != nil { nodeAddressesFunc = kl.cloudResourceSyncManager.NodeAddresses } var setters []func(ctx context.Context, n *v1.Node) error setters = append(setters, nodestatus.NodeAddress(kl.nodeIPs, kl.nodeIPValidator, kl.hostname, kl.hostnameOverridden, kl.externalCloudProvider, kl.cloud, nodeAddressesFunc),
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Tue Jun 04 06:25:43 UTC 2024 - 31.1K bytes - Viewed (0) -
pkg/kubelet/kubelet_pods.go
func (kl *Kubelet) sortPodIPs(podIPs []string) []string { ips := make([]string, 0, 2) var validPrimaryIP, validSecondaryIP func(ip string) bool if len(kl.nodeIPs) == 0 || utilnet.IsIPv4(kl.nodeIPs[0]) { validPrimaryIP = utilnet.IsIPv4String validSecondaryIP = utilnet.IsIPv6String } else { validPrimaryIP = utilnet.IsIPv6String validSecondaryIP = utilnet.IsIPv4String }
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Fri Jun 14 16:09:17 UTC 2024 - 101.2K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.29.md
- The `--bind-address` parameter in kube-proxy is misleading, no port is opened with this address. Instead it is translated internally to "nodeIP". The nodeIPs for both families are now taken from the Node object if `--bind-address` is unspecified or set to the "any" address (0.0.0.0 or ::). It is recommended to leave `--bind-address` unspecified, and in particular avoid to set it to localhost (127.0.0.1...
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Wed Jun 12 03:42:38 UTC 2024 - 324.5K bytes - Viewed (0)