On 5/10/22 18:24, 'james beck' via kubernetes-sig-node wrote:
> I met a question that I used helm to install
> node-feature-discovery-0.11.0.Then nfd-topology-updater creates the CR
> that says "Topology Policies: None". But I set
> topologyPolicyName="restricted".And I saw the logs of the kubelet to
> prove it.So how I deal with it .How my nfd-topology-updater can detect
> the topology policies?Or please provide me with a solution to find the
At the moment, the nfd-topology-updater needs to access and read the
kubelet config to learn and report the topology manager policy. Please
make sure to set correctly the `-kubelet-config-file` option of the
nfd-topology-updater, and to pass the path to the kubelet config file.
the nfd-topology-updater will emit a log line like
detected kubelet Topology Manager policy "restricted"
to report back the topology policy which was detected.
SWE @ Red Hat