- During device plugin allocation, resources requested by the pod can only be allocated if the device plugin has registered itself to kubelet AND healthy devices are present on the node to be allocated. If these conditions are not sattsfied, the pod would fail with `UnexpectedAdmissionError` error. ([#117738](https://github.com/kuber...

- During device plugin allocation, resources requested by the pod can only be allocated if the device plugin has registered itself to kubelet AND healthy devices are present on the node to be allocated. If these conditions are not sattisfied, the pod would fail with `UnexpectedAdmissionError` error. ([#116337](https://github.com/kube...

- Until this release, the iscsi plugin was waiting 10 seconds for a path to appear in the device list. However this timeout is not enough, or is less than the default device discovery timeout in most systems, which prevents certain devices from being discovered. This timeout has been raised to 30 seconds, which should help to avoid mount issues due to device discovery. ([#78475](https://github.com/kubernetes/kubernetes/pull/78475), [@humblec](https://github.com/humblec))...

([#63176](https://github.com/kubernetes/kubernetes/pull/63176), [@bswartz](https://github.com/bswartz))

* Fix issue where on re-registration of device plugin, `allocatable` was not getting updated. This issue makes devices invisible to the Kubelet if device plugin restarts. Only work-around, if this fix is not there, is to restart the kubelet and then start device plugin. ([#63118](https://github.com/kubernetes/kubernetes/pull/63118), [@vikaschoudhary16](https://github.com/vikaschoudhary16))

name: TensorFlow Lite in Play Services issue
about: Use this template for issues with TensorFlow Lite in Google Play Services
labels: 'comp:lite-in-play-services'

---

**System information**
- Android Device information (use `adb shell getprop ro.build.fingerprint`
  if possible):
- TensorFlow Lite in Play Services SDK version (found in `build.gradle`):
- Google Play Services version
  (`Settings` > `Apps` > `Google Play Services` > `App details`):

ifyapp\u0008appchizi\u0008applinzi\napps-1and1\u000eappspacehosted\u0013appspaceusercontent\u0007appspot\u0006atmeta\u000eauiusercontent\u0010authgear-staging\u000cauthgearapps\u000cawsapprunner\u0007awsapps\u0014awsglobalaccelerator\u000ebalena-devices\u000bbarsycenter\u000bbarsyonline\u000ebase44-sandbox\u0007blogdns\u0008blogspot\u0008blogsyte\u0006boutir\u0007bplaced\rbuiltwithdark\u000cbumbleshrimp\u0005cafjs\u0012canva-hosted-embed\u0009canvacode\rcdn77-storage\u0007cechire\u0007cf-ipfs\nc...

servep2p.com
servepics.com
servequake.com
server-on.net
servername.us
servers.run
servesarcasm.com
service.gov.scot
service.gov.uk
service.one
servicebus.windows.net
services
services.aero
setagaya.tokyo.jp
seto.aichi.jp
setouchi.okayama.jp
settsu.osaka.jp
sevastopol.ua
seven
sew
sex
sex.hu
sex.pl
sexy
sf.no
sfr
sg

IPv4/IPv6 dual-stack has been reimplemented for 1.20 to support dual-stack Services, based on user and community feedback. If your cluster has dual-stack enabled, you can create Services which can use IPv4, IPv6, or both, and you can change this setting for existing Services. Details are available in updated [IPv4/IPv6 dual-stack docs](https://docs.k8s.io/concepts/services-networking/dual-stack/), which cover the nuanced array of options.

jmp

// jnj : Johnson & Johnson Services, Inc.
// https://www.iana.org/domains/root/db/jnj.html
jnj

// joburg : ZA Central Registry NPC trading as ZA Central Registry
// https://www.iana.org/domains/root/db/joburg.html
joburg

// jot : Amazon Registry Services, Inc.
// https://www.iana.org/domains/root/db/jot.html
jot

// joy : Amazon Registry Services, Inc.