What happened:
Resources that will be managed by NFD topology-updater are only discovered during startup.
If a device plugin registers itself with kubelet after NFD topology-updater is already running the NRT will never be updated with new resources.

Resource discovery link
Ignoring resources not present during startup link.

It may cause issues when nfd is restarted alongside device plugins, in this case NRT will stop reporting some resources.

What you expected to happen:

When device plugin is created after NFD start new resources should be reported without the need of restarting NFD.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Network plugin and version (if this is a network-related bug):
• Others: