mirror of
https://github.com/kubernetes-sigs/node-feature-discovery.git
synced 2025-03-30 19:54:46 +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. |
||
|---|---|---|
| .. | ||
| annotations_labels.go | ||
| doc.go | ||
| expression.go | ||
| expression_test.go | ||
| feature.go | ||
| generate.sh | ||
| generated.pb.go | ||
| generated.proto | ||
| register.go | ||
| rule.go | ||
| rule_test.go | ||
| types.go | ||
| zz_generated.deepcopy.go | ||