1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/node-feature-discovery.git synced 2025-03-16 13:28:18 +00:00
Commit graph

11 commits

Author SHA1 Message Date
Markus Lehtonen
24f2c26b70 Update references for v0.14.6 release 2024-03-28 11:06:17 +02:00
Markus Lehtonen
ef588a5227 Update references to release v0.14.5
Manually generated with:

    ./hack/prepare-release.sh -g 1.20.14 v0.14.5
2024-03-15 11:05:41 +02:00
Markus Lehtonen
a643a5e2df Update references to release v0.14.4 2023-12-20 15:43:41 +02:00
Markus Lehtonen
07a19a929a Update references to release v0.14.3 2023-10-23 11:30:57 +03:00
Carlos Eduardo Arango Gutierrez
720ef4614c
Update references to release v0.14.2
Signed-off-by: Carlos Eduardo Arango Gutierrez <eduardoa@nvidia.com>
2023-10-09 20:12:11 +02:00
Markus Lehtonen
91c2666b9c Update references to release v0.14.1
Generated with:

    hack/prepare-release.sh -g 1.20.8 v0.14.1
2023-09-20 10:51:03 +03:00
Carlos Eduardo Arango Gutierrez
61afda1f56
[release-0.14] Update references to release v0.14
Signed-off-by: Carlos Eduardo Arango Gutierrez <eduardoa@nvidia.com>
2023-09-07 15:19:46 +02:00
Markus Lehtonen
06b333db1e nfd-topology-updater: add metrics support
For now, add only one metric, a counter for the errors occurring while
scanning pod resources on the node.
2023-08-04 16:48:37 +03:00
Markus Lehtonen
f13ed2d91c nfd-topology-updater: update NodeResourceTopology objects directly
Drop the gRPC communication to nfd-master and connect to the Kubernetes
API server directly when updating NodeResourceTopology objects.
Topology-updater already has connection to the API server for listing
Pods so this is not that dramatic change. It also simplifies the code
a lot as there is no need for the NFD gRPC client and no need for
managing TLS certs/keys.

This change aligns nfd-topology-updater with the future direction of
nfd-worker where the gRPC API is being dropped and replaced by a
CRD-based API.

This patch also update deployment files and documentation to reflect
this change.
2022-12-08 11:03:22 +02:00
Markus Lehtonen
e342076a5e deployment: clean up base/topologyupdater-daemonset
The base should really have the very bare minimum. Remove all redundant
(at default-value) args and move the others to the specific
topologyupdater kustomize component. This also makes these settings
re-usable in user-specific overlays (that are not based on
topologyupdater-daemonset).
2021-10-06 21:42:31 +03:00
Swati Sehgal
a2c066dc0d topologyupdater: manifests: topologyupdater deployment files
- create an overlay for deployment of all components
- create an overlay for just topologyupdater deployment (to be deployed in
  conjunction with the default overlay)
- create a separate overlay for deployment of master and topologyupdater-job

Signed-off-by: Swati Sehgal <swsehgal@redhat.com>
2021-09-21 10:48:10 +01:00