mirrors/node-feature-discovery
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/node-feature-discovery.git synced 2024-12-14 11:57:51 +00:00
Code Activity
node-feature-discovery/go.mod

61 lines
2.5 KiB
Modula-2
Raw Normal View History

Switch to using go modules Update go version in Docker build image to v1.12.
2019-11-20 13:41:48 +00:00
module sigs.k8s.io/node-feature-discovery
bump to go 1.16 Signed-off-by: Carlos Eduardo Arango Gutierrez <carangog@redhat.com>
2021-03-24 15:00:36 +00:00
go 1.16
Switch to using go modules Update go version in Docker build image to v1.12.
2019-11-20 13:41:48 +00:00
require (
nfd-worker: use fsnotify for watching for config file changes Add support for detecting configuration file changes via file system notifications (fsnotify). Watches are added for the whole directory chain (up to root directory) so that all changes (even directory renames) affecting the given configuration file path are captured. Previously dynamic (re-)configuration of nfd-worker was implemented by (re-)reading the configuration file on every labeling pass. This was simple and effective, even if a bit wasteful. However, it didn't provide asynchronous configuration updates that will be required for e.g. controlling the "sleep-interval" parameter dynamically which will be implemented by later patches.
2020-11-27 06:26:22 +00:00
github.com/fsnotify/fsnotify v1.4.9
topologyupdater: Bootstrap nfd-topology-updater in NFD - This patch allows to expose Resource Hardware Topology information through CRDs in Node Feature Discovery. - In order to do this we introduce another software component called nfd-topology-updater in addition to the already existing software components nfd-master and nfd-worker. - nfd-master was enhanced to communicate with nfd-topology-updater over gRPC followed by creation of CRs corresponding to the nodes in the cluster exposing resource hardware topology information of that node. - Pin kubernetes dependency to one that include pod resource implementation - This code is responsible for obtaining hardware information from the system as well as pod resource information from the Pod Resource API in order to determine the allocatable resource information for each NUMA zone. This information along with Costs for NUMA zones (obtained by reading NUMA distances) is gathered by nfd-topology-updater running on all the nodes of the cluster and propagate NUMA zone costs to master in order to populate that information in the CRs corresponding to the nodes. - We use GHW facilities for obtaining system information like CPUs, topology, NUMA distances etc. - This also includes updates made to Makefile and Dockerfile and Manifests for deploying nfd-topology-updater. - This patch includes unit tests - As part of the Topology Aware Scheduling work, this patch captures the configured Topology manager scope in addition to the Topology manager policy. Based on the value of both attribues a single string will be populated to the CRD. The string value will be on of the following {SingleNUMANodeContainerLevel, SingleNUMANodePodLevel, BestEffort, Restricted, None} Co-Authored-by: Artyom Lukianov <alukiano@redhat.com> Co-Authored-by: Francesco Romani <fromani@redhat.com> Co-Authored-by: Talor Itzhak <titzhak@redhat.com> Signed-off-by: Swati Sehgal <swsehgal@redhat.com>
2021-05-13 10:55:33 +00:00
github.com/ghodss/yaml v1.0.0
topologyupdater: gRPC API definition Setup the topologyupdater API for gRPC communication of nfd-topology-updater with master We generate pb.go file to reflect latest dependency changes using github.com/golang/protobuf/protoc-gen-go and generate grpc files via: `protoc pkg/topologyupdater/topology-updater.proto --go_out=plugins=grpc:.` Please refer to: https://github.com/k8stopologyawareschedwg/noderesourcetopology-api/blob/master/pkg/apis/topology/v1alpha1/types.go Co-Authored-by: Artyom Lukianov <alukiano@redhat.com> Co-Authored-by: Francesco Romani <fromani@redhat.com> Signed-off-by: Swati Sehgal <swsehgal@redhat.com>
2021-05-13 10:51:15 +00:00
github.com/golang/protobuf v1.5.2
topologyupdater: Bootstrap nfd-topology-updater in NFD - This patch allows to expose Resource Hardware Topology information through CRDs in Node Feature Discovery. - In order to do this we introduce another software component called nfd-topology-updater in addition to the already existing software components nfd-master and nfd-worker. - nfd-master was enhanced to communicate with nfd-topology-updater over gRPC followed by creation of CRs corresponding to the nodes in the cluster exposing resource hardware topology information of that node. - Pin kubernetes dependency to one that include pod resource implementation - This code is responsible for obtaining hardware information from the system as well as pod resource information from the Pod Resource API in order to determine the allocatable resource information for each NUMA zone. This information along with Costs for NUMA zones (obtained by reading NUMA distances) is gathered by nfd-topology-updater running on all the nodes of the cluster and propagate NUMA zone costs to master in order to populate that information in the CRs corresponding to the nodes. - We use GHW facilities for obtaining system information like CPUs, topology, NUMA distances etc. - This also includes updates made to Makefile and Dockerfile and Manifests for deploying nfd-topology-updater. - This patch includes unit tests - As part of the Topology Aware Scheduling work, this patch captures the configured Topology manager scope in addition to the Topology manager policy. Based on the value of both attribues a single string will be populated to the CRD. The string value will be on of the following {SingleNUMANodeContainerLevel, SingleNUMANodePodLevel, BestEffort, Restricted, None} Co-Authored-by: Artyom Lukianov <alukiano@redhat.com> Co-Authored-by: Francesco Romani <fromani@redhat.com> Co-Authored-by: Talor Itzhak <titzhak@redhat.com> Signed-off-by: Swati Sehgal <swsehgal@redhat.com>
2021-05-13 10:55:33 +00:00
github.com/google/go-cmp v0.5.5
github.com/jaypipes/ghw v0.8.1-0.20210827132705-c7224150a17e
topologyupdater: gRPC API definition Setup the topologyupdater API for gRPC communication of nfd-topology-updater with master We generate pb.go file to reflect latest dependency changes using github.com/golang/protobuf/protoc-gen-go and generate grpc files via: `protoc pkg/topologyupdater/topology-updater.proto --go_out=plugins=grpc:.` Please refer to: https://github.com/k8stopologyawareschedwg/noderesourcetopology-api/blob/master/pkg/apis/topology/v1alpha1/types.go Co-Authored-by: Artyom Lukianov <alukiano@redhat.com> Co-Authored-by: Francesco Romani <fromani@redhat.com> Signed-off-by: Swati Sehgal <swsehgal@redhat.com>
2021-05-13 10:51:15 +00:00
github.com/k8stopologyawareschedwg/noderesourcetopology-api v0.0.9
go.mod: update to klauspost/cpuid/v2@v2.0.9 The new version adds AVX512-FP16 (half precision floating-point) support available on Sapphire Rapids. Signed-off-by: Mikko Ylinen <mikko.ylinen@intel.com>
2021-08-02 10:48:34 +00:00
github.com/klauspost/cpuid/v2 v2.0.9
go.mod: update kubernetes to v1.22.0 Update k/k to v1.22.0 and sync all related dependencies with it.
2021-08-12 07:15:47 +00:00
github.com/onsi/ginkgo v1.14.0
github.com/onsi/gomega v1.10.1
nfd-master: patch node object instead of rewriting it When updating node labels and annotations use JSON patches instead of doing a read-modify-write on the whole node object. Patching is already being used in managing extended resources so some of the existing code was re-usable. This patch should mitigate the problem of node update failures caused by race conditions (a change in the node object between our read and write) resulting e.g. in errors/restarts in nfd worker pods.
2020-08-13 14:14:27 +00:00
github.com/smartystreets/assertions v1.2.0
Update k8s dependencies to 1.19.4 Signed-off-by: Artyom Lukianov <alukiano@redhat.com>
2020-11-17 14:39:05 +00:00
github.com/smartystreets/goconvey v1.6.4
go.mod: update kubernetes to v1.22.0 Update k/k to v1.22.0 and sync all related dependencies with it.
2021-08-12 07:15:47 +00:00
github.com/stretchr/testify v1.7.0
Switch to using go modules Update go version in Docker build image to v1.12.
2019-11-20 13:41:48 +00:00
github.com/vektra/errors v0.0.0-20140903201135-c64d83aba85a
go.mod: update golang.org/x/net
2021-08-12 07:54:58 +00:00
golang.org/x/net v0.0.0-20210805182204-aaa1db679c0d
go.mod: update kubernetes to v1.22.0 Update k/k to v1.22.0 and sync all related dependencies with it.
2021-08-12 07:15:47 +00:00
google.golang.org/grpc v1.38.0
go.mod: update dependencies
2021-06-10 07:22:50 +00:00
google.golang.org/protobuf v1.27.1
go.mod: update kubernetes to v1.22.0 Update k/k to v1.22.0 and sync all related dependencies with it.
2021-08-12 07:15:47 +00:00
k8s.io/api v0.22.0
k8s.io/apimachinery v0.22.0
k8s.io/client-go v0.22.0
k8s.io/klog/v2 v2.9.0
topologyupdater: Bootstrap nfd-topology-updater in NFD - This patch allows to expose Resource Hardware Topology information through CRDs in Node Feature Discovery. - In order to do this we introduce another software component called nfd-topology-updater in addition to the already existing software components nfd-master and nfd-worker. - nfd-master was enhanced to communicate with nfd-topology-updater over gRPC followed by creation of CRs corresponding to the nodes in the cluster exposing resource hardware topology information of that node. - Pin kubernetes dependency to one that include pod resource implementation - This code is responsible for obtaining hardware information from the system as well as pod resource information from the Pod Resource API in order to determine the allocatable resource information for each NUMA zone. This information along with Costs for NUMA zones (obtained by reading NUMA distances) is gathered by nfd-topology-updater running on all the nodes of the cluster and propagate NUMA zone costs to master in order to populate that information in the CRs corresponding to the nodes. - We use GHW facilities for obtaining system information like CPUs, topology, NUMA distances etc. - This also includes updates made to Makefile and Dockerfile and Manifests for deploying nfd-topology-updater. - This patch includes unit tests - As part of the Topology Aware Scheduling work, this patch captures the configured Topology manager scope in addition to the Topology manager policy. Based on the value of both attribues a single string will be populated to the CRD. The string value will be on of the following {SingleNUMANodeContainerLevel, SingleNUMANodePodLevel, BestEffort, Restricted, None} Co-Authored-by: Artyom Lukianov <alukiano@redhat.com> Co-Authored-by: Francesco Romani <fromani@redhat.com> Co-Authored-by: Talor Itzhak <titzhak@redhat.com> Signed-off-by: Swati Sehgal <swsehgal@redhat.com>
2021-05-13 10:55:33 +00:00
k8s.io/kubelet v0.0.0
go.mod: update kubernetes to v1.22.0 Update k/k to v1.22.0 and sync all related dependencies with it.
2021-08-12 07:15:47 +00:00
k8s.io/kubernetes v1.22.0
Update k8s dependencies to 1.19.4 Signed-off-by: Artyom Lukianov <alukiano@redhat.com>
2020-11-17 14:39:05 +00:00
sigs.k8s.io/yaml v1.2.0
Switch to using go modules Update go version in Docker build image to v1.12.
2019-11-20 13:41:48 +00:00
)
// The k8s "sub-"packages do not have 'semver' compatible versions. Thus, we
// need to override with commits (corresponding their kubernetes-* tags)
replace (
Update gogo/protobuf and golang.org/x/text Why: - CVE-2020-28851 - CVE-2021-3121 Signed-off-by: Carlos Eduardo Arango Gutierrez <carangog@redhat.com>
2021-02-10 21:13:51 +00:00
github.com/gogo/protobuf => github.com/gogo/protobuf v1.3.2
go.mod: update kubernetes to v1.22.0 Update k/k to v1.22.0 and sync all related dependencies with it.
2021-08-12 07:15:47 +00:00
k8s.io/api => k8s.io/api v0.22.0
k8s.io/apiextensions-apiserver => k8s.io/apiextensions-apiserver v0.22.0
k8s.io/apimachinery => k8s.io/apimachinery v0.22.0
k8s.io/apiserver => k8s.io/apiserver v0.22.0
k8s.io/cli-runtime => k8s.io/cli-runtime v0.22.0
k8s.io/client-go => k8s.io/client-go v0.22.0
k8s.io/cloud-provider => k8s.io/cloud-provider v0.22.0
k8s.io/cluster-bootstrap => k8s.io/cluster-bootstrap v0.22.0
k8s.io/code-generator => k8s.io/code-generator v0.22.0
k8s.io/component-base => k8s.io/component-base v0.22.0
k8s.io/component-helpers => k8s.io/component-helpers v0.22.0
k8s.io/controller-manager => k8s.io/controller-manager v0.22.0
k8s.io/cri-api => k8s.io/cri-api v0.22.0
k8s.io/csi-translation-lib => k8s.io/csi-translation-lib v0.22.0
k8s.io/kube-aggregator => k8s.io/kube-aggregator v0.22.0
k8s.io/kube-controller-manager => k8s.io/kube-controller-manager v0.22.0
k8s.io/kube-proxy => k8s.io/kube-proxy v0.22.0
k8s.io/kube-scheduler => k8s.io/kube-scheduler v0.22.0
k8s.io/kubectl => k8s.io/kubectl v0.22.0
k8s.io/kubelet => k8s.io/kubelet v0.22.0
k8s.io/legacy-cloud-providers => k8s.io/legacy-cloud-providers v0.22.0
k8s.io/metrics => k8s.io/metrics v0.22.0
k8s.io/mount-utils => k8s.io/mount-utils v0.22.0
k8s.io/pod-security-admission => k8s.io/pod-security-admission v0.22.0
k8s.io/sample-apiserver => k8s.io/sample-apiserver v0.22.0
Switch to using go modules Update go version in Docker build image to v1.12.
2019-11-20 13:41:48 +00:00
)
Copy permalink