pprokop 6d98b6150b Fix Topology Manager policy and scope not being updated properly ... NFD is only detecting policy and scope of Topology Manager when NRT object doesn't exist. This means that topologyManagerScope and topologyManagerPolicy attributes won't be updated even if kubelet config was changed to use other TopologyManager policy and scope. Signed-off-by: pprokop <pprokop@nvidia.com>		2023-07-20 16:31:12 +02:00
..
apihelper	generate: update mockery to v2.25.1	2023-04-19 13:33:42 +03:00
apis/nfd/v1alpha1	pkg/utils: migrate KlogDump to structured logging	2023-05-31 14:43:08 +03:00
cpuid	pkg/cpuid: lint fixes	2020-05-20 21:48:06 +03:00
generated	generate: update auto-generated code	2023-04-19 09:49:17 +03:00
labeler	generate: update mockery to v2.25.1	2023-04-19 13:33:42 +03:00
nfd-master	nfd-master: check for nil references in nfdAPIUpdateAllNodes	2023-07-17 17:49:44 +03:00
nfd-topology-gc	Stop ticker in time to avoid memory leak	2023-07-05 18:35:01 +08:00
nfd-topology-updater	Fix Topology Manager policy and scope not being updated properly	2023-07-20 16:31:12 +02:00
nfd-worker	pkg/utils: migrate KlogDump to structured logging	2023-05-31 14:43:08 +03:00
podres	generate: update mockery to v2.25.1	2023-04-19 13:33:42 +03:00
resourcemonitor	topology-updater: migrate to structured logging	2023-05-31 14:43:08 +03:00
topologypolicy	nrt-api: move from v1alpha1 to v1alpha2	2023-02-09 12:29:54 +01:00
utils	pkg/utils: migrate KlogDump to structured logging	2023-05-31 14:43:08 +03:00
version	version: allow undefined version	2020-03-20 07:21:43 +02:00