<unknown>   Normal   Scheduled           pod/nginx-6c975b59f8-gvmjr    Successfully assigned default/nginx-6c975b59f8-gvmjr to minikube
  
  $ kubectl describe pod xxx
  ......
  Events:
    Type    Reason     Age        From               Message
    ----    ------     ----       ----               -------

wzmiuw.gov.pl
x.bg
x.mythic-beasts.com
x.se
x0.com
x0.to
x443.pw
xbox
xen.prgmr.com
xerox
xihuan
xii.jp
xin
xj.cn
xmit.dev
xnbay.com
xs4all.space
xxx
xyz
xz.cn
y.bg
y.se
yabu.hyogo.jp
yabuki.fukushima.jp
yachimata.chiba.jp
yachiyo.chiba.jp
yachiyo.ibaraki.jp
yachts
yaese.okinawa.jp
yahaba.iwate.jp
yahiko.niigata.jp

  127.0.0.1. (Also note that there are currently no command-line arguments
  for the nftables-specific config; you will need to use a config file if
  you want to set the equivalent of any of the `--iptables-xxx` options.)
  
  As this code is still very new, it has not been heavily optimized yet;
  while it is expected to _eventually_ have better performance than the

台湾

// xn--nnx388a ("Taiwan", Chinese, variant) : TW
臺灣

// xn--j1amh ("ukr", Cyrillic) : UA
укр

// xn--mgb2ddes ("AlYemen", Arabic) : YE
اليمن

// xxx : http://icmregistry.com
xxx

// ye : http://www.y.net.ye/services/domain_name.htm
ye
com.ye
edu.ye
gov.ye
net.ye
mil.ye
org.ye

wzmiuw.gov.pl
x.bg
x.mythic-beasts.com
x.se
x0.com
x0.to
x443.pw
xbox
xen.prgmr.com
xerox
xihuan
xii.jp
xin
xj.cn
xmit.dev
xnbay.com
xs4all.space
xxx
xyz
xz.cn
y.bg
y.se
yabu.hyogo.jp
yabuki.fukushima.jp
yachimata.chiba.jp
yachiyo.chiba.jp
yachiyo.ibaraki.jp
yachts
yaese.okinawa.jp
yahaba.iwate.jp
yahiko.niigata.jp

* Set fsGroup by securityContext.fsGroup in azure file. However,f user both sets gid=xxx in mountOptions in azure storage class and securityContext.fsGroup, gid=xxx setting in mountOptions takes precedence. ([#58316](https://github.com/kubernetes/kubernetes/pull/58316), [@andyzhangx](https://github.com/andyzhangx))

- Fix: After a Node is down and take some time to get back to up again, the mount point of the evicted Pods cannot be cleaned up successfully. (#111933) Meanwhile Kubelet will print the log `Orphaned pod "xxx" found, but error not a directory occurred when trying to remove the volumes dir` every 2 seconds. (#105536) ([#116134](https://github.com/kubernetes/kubernetes/pull/116134), [@cvvz](https://github.com/cvvz)) [SIG Node and Storage]

*   Kubectl now outputs <none> for columns specified by -o custom-columns but not found in object, rather than "xxx is not found" ([#51750](https://github.com/kubernetes/kubernetes/pull/51750),[ @jianhuiz](https://github.com/jianhuiz))

* [Part 2] Adding s390x cross-compilation support for gcr.io images in this repo ([#36050](https://github.com/kubernetes/kubernetes/pull/36050), [@gajju26](https://github.com/gajju26))
* kubectl run --rm no longer prints "pod xxx deleted" ([#38429](https://github.com/kubernetes/kubernetes/pull/38429), [@duglin](https://github.com/duglin))

- Fix: After a Node is down and take some time to get back to up again, the mount point of the evicted Pods cannot be cleaned up successfully. (#111933) Meanwhile Kubelet will print the log `Orphaned pod "xxx" found, but error not a directory occurred when trying to remove the volumes dir` every 2 seconds. (#105536) ([#116134](https://github.com/kubernetes/kubernetes/pull/116134), [@cvvz](https://github.com/cvvz)) [SIG Node and Storage]