Extended resources are not synced/cleaned according to state of KPM #77
Description
PowerProfiles advertised as extended resources are not cleaned after uninstalling KPM or deleting PowerProfile for which this extended resource was created.
This leads to a problem in situations in which Container is requesting PowerProfile which existed in the past, but is absent currently. When requested PowerProfile is not found as extended resource on the node, Pod which is requesting it is left in Pending state -> correct and clear behavior, exact reason for Pending state can be found when Describing the Pod. When using PowerProfile that existed in the past, but does not exist currently, Pod is created, and no user facing error is reported. Error message can only be found in power-node-agent logs. Of course no actions are taken in Power Library to assing CPUs, so on... User might no be aware that something is wrong at all.