mirror of
https://github.com/kubernetes-sigs/node-feature-discovery.git
synced 2024-12-14 11:57:51 +00:00
b907d07d7e
Flatten the data structure that stores features, dropping the "domain" level from the data model. That extra level of hierarchy brought little benefit but just caused some extra complexity, instead. The new structure nicely matches what we have in the NodeFeatureRule object (the matchFeatures field of uses the same flat structure with the "feature" field having a value <domain>.<feature>, e.g. "kernel.version"). This is pre-work for introducing a new "node feature" CRD that contains the raw feature data. It makes the life of both users and developers easier when both CRDs, plus our internal code, handle feature data in a similar flat structure.
37 lines
996 B
Protocol Buffer
37 lines
996 B
Protocol Buffer
/*
|
|
Copyright 2019 The Kubernetes Authors.
|
|
|
|
Licensed under the Apache License, Version 2.0 (the "License");
|
|
you may not use this file except in compliance with the License.
|
|
You may obtain a copy of the License at
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing, software
|
|
distributed under the License is distributed on an "AS IS" BASIS,
|
|
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
See the License for the specific language governing permissions and
|
|
limitations under the License.
|
|
*/
|
|
|
|
syntax = "proto3";
|
|
|
|
option go_package = "sigs.k8s.io/node-feature-discovery/pkg/labeler";
|
|
|
|
import "pkg/apis/nfd/v1alpha1/generated.proto";
|
|
|
|
package labeler;
|
|
|
|
service Labeler{
|
|
rpc SetLabels(SetLabelsRequest) returns (SetLabelsReply) {}
|
|
}
|
|
|
|
message SetLabelsRequest {
|
|
string nfd_version = 1;
|
|
string node_name = 2;
|
|
map<string, string> labels = 3;
|
|
v1alpha1.Features features = 4;
|
|
}
|
|
|
|
message SetLabelsReply {
|
|
}
|