pkg syscall (darwin-arm64), const IP_DUMMYNET_GET ideal-int
pkg syscall (darwin-arm64), const IP_FAITH = 22
pkg syscall (darwin-arm64), const IP_FAITH ideal-int
pkg syscall (darwin-arm64), const IP_FW_ADD = 40
pkg syscall (darwin-arm64), const IP_FW_ADD ideal-int
pkg syscall (darwin-arm64), const IP_FW_DEL = 41
pkg syscall (darwin-arm64), const IP_FW_DEL ideal-int

  repeated string command = 6;
}

// IP address information for entries in the (plural) PodIPs field.
// Each entry includes:
//
// 	IP: An IP address allocated to the pod. Routable at least within the cluster.
message PodIP {
  // ip is an IP address (IPv4 or IPv6) assigned to the pod
  optional string ip = 1;
}

// PodList is a list of Pods.
message PodList {

pkg syscall (netbsd-arm64-cgo), const IP_RECVTTL = 23
pkg syscall (netbsd-arm64-cgo), const IP_RECVTTL ideal-int
pkg syscall (netbsd-arm64-cgo), const IP_RETOPTS = 8
pkg syscall (netbsd-arm64-cgo), const IP_RETOPTS ideal-int
pkg syscall (netbsd-arm64-cgo), const IP_RF = 32768
pkg syscall (netbsd-arm64-cgo), const IP_RF ideal-int
pkg syscall (netbsd-arm64-cgo), const IP_TOS = 3

- the IP allocator in v1.17.0 can return errors such as `the cluster IP <ip> for service <service-name> is not within the service CIDR <cidr>; please recreate` in the logs of the kube-apiserver. The cause is incorrect CIDR calculations if the service CIDR (`--service-cluster-ip-range`) is set to bits lower than `/16`. This is fixed in http://issue.k8s.io/86534 and will be resolved in v1.17.1....

* Only use the first IP address got from instance metadata. This is because Azure CNI would set up a list of IP addresses in instance metadata, while only the first one is the Node's IP. ([#71736](https://github.com/kubernetes/kubernetes/pull/71736), [@feiskyer](https://github.com/feiskyer))

#### Load Balancing
* [stable] Source IP Preservation - change Cloud load-balancer strategy to health-checks and respond to health check only on nodes that host pods for the service. See [Create an External Load Balancer - Preserving the client source IP](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip).
  Two annotations have been promoted to API fields:

### Bug or Regression

- EndpointSlice IP validation now matches Endpoints IP validation. ([#101084](https://github.com/kubernetes/kubernetes/pull/101084), [@robscott](https://github.com/robscott)) [SIG Apps and Network]

    * 3. Maximum of two entries is allowed in `--service-cluster-ip-range` and they are validated to be dual stacked `i.e. --service-cluster-ip-range=<v4>,<v6> or --service-cluster-ip-range=<v6>,<v4>`
    * 4. Max 20 bit for range (min network bits `<v6>/108` or <v4>/12)

* Bump ip-masq-agent to v2.1.1 ([#67916](https://github.com/kubernetes/kubernetes/pull/67916), [@MrHohn](https://github.com/MrHohn))
    * - Update debian-iptables image for CVEs.
    * - Change chain name to IP-MASQ to be compatible with the
    * pre-injected masquerade rules.

- Support [service.beta.kubernetes.io/azure-pip-ip-tags] annotations to allow customers to specify ip-tags to influence public-ip creation in Azure [Tag1=Value1, Tag2=Value2, etc.] ([#94114](https://github.com/kubernetes/kubernetes/pull/94114), [@MarcPow](https://github.com/MarcPow)) [SIG Cloud Provider]