- 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 or ::1) ([#1195...

- Kube-proxy will now warn at startup if the configuration seems inconsistent
  with respect to IP families. (For example, if you have an IPv4 node IP, but
  `--cluster-cidr` is IPv6.) ([#119003](https://github.com/kubernetes/kubernetes/pull/119003), [@danwinship](https://github.com/danwinship)) [SIG Network]

labels.user_given_name=Prénom
labels.givenName=Prénom (nom donné)
labels.user_surname=Nom de famille
labels.surame=Nom de famille
labels.user_mail=E-mail
labels.mail=E-mail
labels.user_employeeNumber=Numéro d'employé
labels.employeeNumber=Numéro d'employé
labels.user_telephoneNumber=Numéro de téléphone

   *
   * <p><b>Warning:</b> in most circumstances it is better to set a per-cache {@linkplain
   * #maximumSize(long) maximum size} instead of using soft references. You should only use this
   * method if you are well familiar with the practical consequences of soft references.
   *
   * <p><b>Note:</b> when this method is used, the resulting cache will use identity ({@code ==})
   * comparison to determine equality of values.
   *

express
express.aero
express.val.run
extraspace
ezproxy.kuleuven.be
f.bg
f.se
f5.si
fage
fail
fairwinds
faith
fakefur.jp
fam.pk
family
familyds.com
familyds.net
familyds.org
fan
fans
fantasyleague.cc
far.br
farm
farmers
farsund.no
fashion
fashionstore.jp
fast
fastly-edge.com
fastly-terrarium.com
fastlylb.net

express
express.aero
express.val.run
extraspace
ezproxy.kuleuven.be
f.bg
f.se
f5.si
fage
fail
fairwinds
faith
fakefur.jp
fam.pk
family
familyds.com
familyds.net
familyds.org
fan
fans
fantasyleague.cc
far.br
farm
farmers
farsund.no
fashion
fashionstore.jp
fast
fastly-edge.com
fastly-terrarium.com
fastlylb.net

// Submitted by Rony Weng <******@****.***>
dscloud.biz
direct.quickconnect.cn
dsmynas.com
familyds.com
diskstation.me
dscloud.me
i234.me
myds.me
synology.me
dscloud.mobi
dsmynas.net
familyds.net
dsmynas.org
familyds.org
direct.quickconnect.to
vpnplus.to

// Tabit Technologies Ltd. : https://tabit.cloud/

- On single-stack configured (IPv4 or IPv6, but not both) clusters, Services which are both headless (no clusterIP) and selectorless (empty or undefined selector) will report `ipFamilyPolicy RequireDualStack` and will have entries in `ipFamilies[]` for both IPv4 and IPv6.  This is a change from alpha, but does not have any impact on the manually-specified Endpoints and EndpointSlices for the Service. ([#99555](https://github.com/kubernetes/kubernetes/pull/99555), [@thockin](https://github.com/thockin))...

- The `Service.spec.ipFamilyPolicy` field is now *required* in order to create or update a Service as dual-stack.  This is a breaking change from the beta behavior.  Previously the server would try to infer the value of that field from either `ipFamilies` or `clusterIPs`, but that caused ambiguity on updates.  Users who want a dual-stack Service MUST specify `ipFamilyPolicy` as either "PreferDualStack" or "RequireDualStack". ([#96684](https://github.com/kubernetes/kubernetes/pull/96684), [@thoc...