Stop relying on unstructured data in network performance KPI codebase #1757
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
What would you like to be added:
Instead of operating on Unstructured items, we want to define our type the same way built-in APIs are defined,
Example:
https://github.com/kubernetes/sample-controller/blob/master/pkg/apis/samplecontroller/v1alpha1/types.go
In network_performance_measurement.go , we have a CR NetworkTestRequest update events being received.
These objects need to be handled using defined types , but instead of unstructured items.
Why is this needed:
Operating on unstructured (if not needed), isn't a good pattern - this code would be much simpler if operating on the type itself.
The text was updated successfully, but these errors were encountered: